[issue8597] build out-of-line asm on Windows

New submission from Zooko O'Whielacronx : I maintain a Python package which comes with assembly optimizations -- http://tahoe-lafs.org/trac/pycryptopp . Someone was porting this package to Win64 today and discovered that distutils couldn't build it because the Microsoft compiler on Win64 doesn

[issue8595] Explain the default timeout in http-client-related libraries

Senthil Kumaran added the comment: On Sun, May 02, 2010 at 03:45:09AM +, Julian wrote: > Note: I am not arguing here that this SHOULD be done - it would > break existing applications, especially those that were written > before Python 2.6 - merely that it COULD be done. I get your point, Ju

[issue8596] crypt blowfish 'ignores' salt

New submission from pvo : Blowfish crypt uses a 128 bit salt, not only the letters [./a-zA-Z0-9]. Despite the different salts, crypt ignores the salt and produces identical encrypted passwords. The problem occurs on FreeBSD 7.2 with Python 2.5.5 (r255:77872) and Python 2.6.4 (r264:7570) (both

[issue8595] Explain the default timeout in http-client-related libraries

Julian added the comment: @orsenthil: Consider the definition of httplib.HTTPConnection.__init__(), in Python 2.6. def __init__(self, host, port=None, strict=None, timeout=socket._GLOBAL_DEFAULT_TIMEOUT): This could be replaced with: def __init__(self, host, port=None,

[issue8557] subprocess PATH semantics and portability

Dave Abrahams added the comment: I've uploaded a new probe.py that contains a win32 Popen wrapper that I think acts just like *nix's Popen w.r.t. PATH and environment (pass --fix to demonstrate). I suggest using this or an equivalent wrapper for Win32, and documenting the fact that with shel

[issue8595] Explain the default timeout in http-client-related libraries

Senthil Kumaran added the comment: I am not sure, there can be a default timeout value for client libraries like httplib and urllib2. Socket connection do have timeout and as you may have figured out already, the option in httplib and urllib methods is to set/override the socket._GLOBAL_DEF

[issue8583] Hardcoded namespace_separator in the cElementTree.XMLParser

Dmitry Chichkov added the comment: This patch does not modify the existing behavior of the library. The namespace_separator parameter is optional. Parameter already exists in the EXPAT library, but it is hard coded in the cElementTree.XMLParser code. Fredrik, yes, namespaces are a fundamental

[issue8595] Unexpected default timeout in http-client-related libraries

New submission from Julian : Since Python 2.6, httplib has offered a timeout parameter for fetches. As the documentation explains, if this parameter is not provided, it uses the global default. What the document doesn't explain is httplib builds on top of the socket library. The socket librar

[issue8214] Add exception logging function to syslog module

Sean Reifschneider added the comment: Switched to using assertTrue/assertFalse. -- Added file: http://bugs.python.org/file17179/logexception5.patch ___ Python tracker ___ ___

[issue8214] Add exception logging function to syslog module

Benjamin Peterson added the comment: You shouln't use fail*. They're deprecated. -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue8550] Expose SSL contexts

Antoine Pitrou added the comment: New patch with docs. -- Added file: http://bugs.python.org/file17178/sslcontext2.patch ___ Python tracker ___ __

[issue8214] Add exception logging function to syslog module

Sean Reifschneider added the comment: Changed to use import_module. -- Added file: http://bugs.python.org/file17177/logexception4.patch ___ Python tracker ___ ___

[issue1533] Bug in range() function for large values

Changes by Alexander Belopolsky : Removed file: http://bugs.python.org/file17175/bltinmodule4.diff ___ Python tracker ___ ___ Python-bugs-list

[issue1533] Bug in range() function for large values

Changes by Alexander Belopolsky : Added file: http://bugs.python.org/file17176/bltinmodule4.diff ___ Python tracker ___ ___ Python-bugs-list ma

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: This patch, bltinmodule4.diff, seems to work for all cases. Mark, It looks like I came up with almost the same logic as you did. The only difference that I can see is that your code does not check that nb_int returns an integer. Also I put repeated

[issue8214] Add exception logging function to syslog module

Brian Curtin added the comment: The test file should use test_support.import_module("syslog") instead of the try/except, which would then make the skip decorators unnecessary. -- nosy: +brian.curtin ___ Python tracker

[issue8214] Add exception logging function to syslog module

Sean Reifschneider added the comment: Thanks for the review Jack. I was very tempted to split it into C and Python components, but I decided against it because it's so close to the 2.7 release. I think it would be best to defer that for the Python 3 release, because of potential packaging issu

[issue8214] Add exception logging function to syslog module

Antoine Pitrou added the comment: Oh, well, sorry. That's what you are already doing. Forget me :) -- ___ Python tracker ___ ___ Pytho

[issue8214] Add exception logging function to syslog module

Antoine Pitrou added the comment: Rewriting another implementation of traceback formatting in C is bad. Just import the "traceback" module and call the desired function in that module. -- nosy: +pitrou versions: -Python 2.7 ___ Python tracker

[issue8594] Add a "source_address" option to ftplib

Antoine Pitrou added the comment: You should not use find_unused_port(), because it causes problems on some Windows buildbot. Also, there's something fishy in your patch, because you never set self.source_address. -- ___ Python tracker

[issue8557] subprocess PATH semantics and portability

R. David Murray added the comment: I didn't run the script. I have now, but I'm not clear from its output what each test is actually doing, and don't really have the time to figure it out from the code right now. I think it is probably more efficient to just ask you what your suggestion is

[issue8550] Expose SSL contexts

Antoine Pitrou added the comment: Here is a patch exposing SSL contexts as the "SSLContext" class. Also, SSL sockets are refactored to create a standalone SSLContext object, unless you create them using the new SSLContext.wrap_socket(). Please note that SSLContexts do not expose much more inf

[issue1661754] ftplib passive ftp problem on multihomed clients

Giampaolo Rodola' added the comment: Issue 8594 is related with this one. -- superseder: -> Add a "source_address" option to ftplib ___ Python tracker ___ ___

[issue8594] Add a "source_address" option to ftplib

New submission from Giampaolo Rodola' : Similarly to issue 3972 the patch in attachment adds a new "source_address" option to FTP class to bind to a specific address when connecting to a remote FTP server. It must be noted that this gets done for both control and passive data connections (cli

[issue8593] Improve c-api/arg.rst

Antoine Pitrou added the comment: Patch uploaded at http://codereview.appspot.com/979047 -- ___ Python tracker ___ ___ Python-bugs-lis

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Alexander, I think it should be as simple as replacing the if (!PyInt_Check(ilow) && ...) block with something like this: if (!PyInt_Check(ilow) && !PyLong_Check(ilow)) { PyNumberMethods *nb = Py_TYPE(ilow)->tp_as_number;

[issue8214] Add exception logging function to syslog module

Sean Reifschneider added the comment: Jack Diederich commented: I don't have my tracker login on this computer so I'll post here. I'd +1 on making the module python with just the core functionality imported from C (it releases the GIL when doing IO). Then you could replace the few hundred line

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: Mark, I did not see your last comment before uploading the last patch. I think your suggestion to bypass PyNumber_Long will fix the new/old style classes discrepancy. -- ___ Python tracker

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: I am attaching a patch which does not crash or leak (as tested with -R :) and adds a unit test for OP's case. The problem, however is that it does not work if new style classes are used in the test case. See disabled (with if 0) test in the patch. I'l

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: A couple of suggestions regarding the patch: (1) I'd suggest leaving the first part of handle_range_longs intact, up to and including the "/* ilow and ihigh correct now; do istep */" block. Then build out the three "if (!PyInt_Check(...)) ..." blocks below t

[issue1533] Bug in range() function for large values

Changes by Mark Dickinson : -- resolution: out of date -> status: closed -> open ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: > Hmm, maybe there is a 2.7 bug here after all: Yes, indeed! Which is why I was suggesting 'wont fix' rather than 'out of date' :) The bltinmodule2.diff patch from Robert causes a segfault in test_builtin on my system; I haven't looked at the patch itself

[issue1533] Bug in range() function for large values

Changes by Alexander Belopolsky : -- assignee: -> belopolsky nosy: +belopolsky -Alexander.Belopolsky ___ Python tracker ___ ___ Python

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: Robert, Your patch segfaults on Lib/test/test_builtin.py, but I agree with the approach. I'll see if it is easy to fix. -- ___ Python tracker __

[issue6822] Error calling .storlines from ftplib

Giampaolo Rodola' added the comment: Attached is a patch which fixes FTP_TLS class as well and changes the test server a little bit. Shouldn't retrlines() suffer the same issue? -- assignee: -> giampaolo.rodola nosy: +giampaolo.rodola versions: +Python 3.1, Python 3.2 -Python 3.0 Adde

[issue7245] better Ctrl-C support in pdb (program can be resumed) (issue216067)

Ilya Sandler added the comment: a note on testing: it should be possible to integrate the tests into existing test_pdb.py by simply placing subprocess based tests next to doctest-based tests. This way pdb tests will at least be in a single module. (this is an approach taken by a patch in htt

[issue8557] subprocess PATH semantics and portability

Dave Abrahams added the comment: @r.david.murray: did you try running my test? I think it shows that we are pretty darned close to fully portable. I believe we could fix Popen to make it fully portable pretty easily. In fact, there may be a pure-python fix. Documenting the differences wou

[issue1533] Bug in range() function for large values

Robert Bradshaw added the comment: Thank you Alexander. Yes, there is still an issue for large operands, and the attached patch does fix it. Floats are explicitly checked for and rejected by PyArg_ParseTuple for the "l" format (as called by builtin_range) so to preserve this behavior we can e

[issue8593] Improve c-api/arg.rst

New submission from Antoine Pitrou : This patch fixes, reorders and improves c-api/arg.rst. I would even suggest to go further and single out a couple of "most useful" formats ('s', 'y*', 'i', 'l'...) so that people don't get lost in all the possibilities. -- assignee: d...@python com

[issue4485] fast swap of "default" Windows python versions

Andreas Lemke added the comment: Python 2.5, 2.6, 3.0, etc. are not fully compatible programming languages. And we cannot expect that there will ever be the one and only ultimate version of Python (hopefully). Many of us need to have more than one of them installed simultaneously. Upon openin

[issue8592] 'y' does not check for embedded NUL bytes

New submission from Antoine Pitrou : The documentation for the 'y' format (PyArg_ParseTuple and friends) states that: « The bytes object must not contain embedded NUL bytes; if it does, a TypeError exception is raised. » But, reading Python/getargs.c, the strlen() check is actually missing in

[issue8583] Hardcoded namespace_separator in the cElementTree.XMLParser

Fredrik Lundh added the comment: Namespaces are a fundamental part of the XML information model (both xpath and infoset) and all modern XML document formats, so I'm not sure what problem you're trying to solve by pretending that they don't exist. It's a bit like modifying "import foo" to work

[issue8591] update mkpkg to latest coding standards

Dan Buch added the comment: I probably shouldn't have dropped the PEP8 bomb so much as stated that I feel the module could use some updating. It's my (very much potentially wrong) understanding that `distutils2.mkpkg` isn't considered library code so much as the guts of a script. The reas

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

Mark Dickinson added the comment: Final patch (?!) fixes all the test failures due to exception precedence issues. -- Added file: http://bugs.python.org/file17167/issue8567_3.patch ___ Python tracker __

[issue8572] httplib getheader() throws error instead of default

Senthil Kumaran added the comment: previous patch had a typo and a mistake. uploading the correct one. -- Added file: http://bugs.python.org/file17166/issue8572.diff ___ Python tracker _

[issue8572] httplib getheader() throws error instead of default

Changes by Senthil Kumaran : Removed file: http://bugs.python.org/file17165/issue8572.diff ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8572] httplib getheader() throws error instead of default

Senthil Kumaran added the comment: It seems that 3.x behavior is correct. I am quoting a relevant section from rfc 2616. """ It MUST be possible to combine the multiple header fields into one "field-name: field-value" pair, without changing the semantics of the message, by appending each sub

[issue8407] expose signalfd(2) and sigprocmask(2) in the signal module

Changes by Antoine Pitrou : -- nosy: +gregory.p.smith -gps ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: On Sat, May 1, 2010 at 10:59 AM, Mark Dickinson wrote: > > Mark Dickinson added the comment: > > Decimal is behaving in exactly the same way as MyInt, isn't it? > What do you get for range(MyInt(20), MyInt(20))? > Hmm, maybe there is a 2.7 bug here afte

[issue8591] update mkpkg to latest coding standards

Éric Araujo added the comment: Pepeightification is ok for things like whitespace that do not break compatibility (don’t waste time doing it manually though, we have automated tools that can be used to reindent the whole of Distutils2). However, renaming classes and functions has to be done w

[issue8407] expose signalfd(2) and sigprocmask(2) in the signal module

Changes by Jean-Paul Calderone : -- nosy: +gps ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8591] update mkpkg to latest coding standards

New submission from Dan Buch : On first glance, `distutils2.mkpkg` does not reflect the latest and greatest in Python coding standards. I'd like to take a stab at PEP-(7|8)'ing the whole thing, although I know there are other issues open to add features to the module, so I don't want to cause

[issue8407] expose signalfd(2) and sigprocmask(2) in the signal module

Jean-Paul Calderone added the comment: One open question regarding interaction with threading. sigprocmask's behavior in a multithreaded program is unspecified. pthread_sigmask should be used instead. I could either expose both of these and let the caller choose, or I could make signal.sig

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Paul Moore added the comment: Might work - but the only ones that were actually failing for me were test_multiprocessing and test_smtplib. So I'm not quite sure where/when the error would be raised on the remaining 2 (socket & httplib). But I'll keep it in mind. To be honest, the remaining t

[issue8514] Create fsencode() and fsdecode() functions in os.path

Antoine Pitrou added the comment: In posixmodule.c, the following snippet doesn't make sense anymore: if (k == NULL) { PyErr_Clear(); continue; } If memory allocation of the bytes object fails, we should error out.

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

Mark Dickinson added the comment: Better patch, that checks exception precedence for every test case when EXTENDEDERRORTEST is defined. With this patch, I get 11 test failures in test_decimal (down from 50 test failures before the Decimal._fix fix). Now we just have to track down the remaini

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Decimal is behaving in exactly the same way as MyInt, isn't it? What do you get for range(MyInt(20), MyInt(20))? -- ___ Python tracker ___

[issue1533] Bug in range() function for large values

Alexander Belopolsky added the comment: On Sat, May 1, 2010 at 3:50 AM, Mark Dickinson wrote: > > Mark Dickinson added the comment: > > Alexander: range *does* still accept such arguments (in 2.7);  just not > floats: > from decimal import Decimal range(Decimal(20), Decimal(20)) > [

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Michael Foord added the comment: What does issue 8522 have to do with it - did you mean a different issue? In unittest it could catch the UnicodeEncodeError and write the ascii repr instead. -- ___ Python tracker

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

Changes by Mark Dickinson : Removed file: http://bugs.python.org/file17162/issue8567.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

Changes by Mark Dickinson : Added file: http://bugs.python.org/file17163/issue8567.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8567] decimal module doesn't respect precedence rules for exceptional conditions

Mark Dickinson added the comment: Here's a quick fix for Decimal._fix, that just makes sure that it raises exceptions in the appropriate order. I'll also try to apply the check_precedence methodology included in this patch to every single testcase. I don't think it's reasonable to add this t

[issue8586] test_imp.py test failures on Py3K Mac OS X

Changes by R. David Murray : -- assignee: -> barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

R. David Murray added the comment: Victor has proposed a patch for the traceback problem for regrtest, I think. I haven't looked at it, but I wonder if there is something that can instead be done to make unittest work in cases like this when run in an ascii terminal. See issue 8522. --

[issue8586] test_imp.py test failures on Py3K Mac OS X

Changes by R. David Murray : -- assignee: barry -> nosy: +ezio.melotti, flox ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

R. David Murray added the comment: Could you special case the test_socket test by checking for the error that Windows sometimes throws and retrying (in a loop for say a second)? Not ideal, but probably better than adding a sleep or throwing away the test :) -- nosy: +r.david.murray

[issue8581] Logging handlers do not handle double-closing very well

Jason Baker added the comment: Vinay, I don't necessarily disagree with you. However, this appears to be a pretty trivial change. If there is a 2.6.6, I think this should go in it. -- ___ Python tracker ___

[issue4388] test_cmd_line fails on MacOS X

Michael Foord added the comment: This passes for me in Mac OS X Terminal (a UTF8 terminal) but fails in iTerm (an ascii terminal) on both 31-maint and py3k. -- ___ Python tracker __

[issue8588] test_urllib2.py test failures on Py3K Mac OS X

Michael Foord added the comment: Same failure on 31-maint. -- versions: +Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mailin

[issue8590] test_httpservers.CGIHTTPServerTestCase failure on 3.1-maint Mac OS X

New submission from Michael Foord : A failure in test_httpservers.py on 31-maint (not failing in py3k) on Mac OS X 10.6.3: test_post (__main__.CGIHTTPServerTestCase) ... Traceback (most recent call last): File "/private/var/folders/WD/WDk8J3uFE7OM9tRer5Oy4E+++TI/-Tmp-/tmpv_ZniR/cgi-bin/file

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Antoine Pitrou added the comment: Vinay, are you ok with the proposed patch? -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-b

[issue8586] test_imp.py test failures on Py3K Mac OS X

Changes by Antoine Pitrou : -- assignee: -> barry components: +Tests nosy: +barry stage: unit test needed -> needs patch ___ Python tracker ___ __

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

Changes by Antoine Pitrou : -- assignee: -> brett.cannon components: +Tests nosy: +brett.cannon, haypo ___ Python tracker ___ ___ Pyth

[issue8589] test_warnings.CEnvironmentVariableTests.test_nonascii fails under an ascii terminal

New submission from Michael Foord : If you run test_warnings.py under an ascii terminal (at least on Mac OS X) then test_warnings.CEnvironmentVariableTests.test_nonascii fails. Perhaps the test should be skipped? == FAIL: tes

[issue8588] test_urllib2.py test failures on Py3K Mac OS X

Changes by Michael Foord : -- assignee: -> orsenthil nosy: +orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue8588] test_urllib2.py test failures on Py3K Mac OS X

New submission from Michael Foord : Failures on py3k, Mac OS X 10.6.3. == ERROR: test_proxy_https (__main__.HandlerTests) -- Traceback (most recent call last):

[issue8587] test_import.py test failures on Py3K Mac OS X

Michael Foord added the comment: Assuming this is actually the same problem as issue 8586. -- resolution: -> duplicate stage: -> committed/rejected status: open -> closed ___ Python tracker __

[issue8586] test_imp.py test failures on Py3K Mac OS X

Michael Foord added the comment: So I'm assuming issue 8587 (same failure in test_import.py) is a duplicate of this. I'll close 8587. -- ___ Python tracker ___ _

[issue8586] test_imp.py test failures on Py3K Mac OS X

Michael Foord added the comment: I see similar failures (failing to unlink weird paths from support.py) in: test_imp.py, test_import.py, test_pydoc.py, test_runpy.py, -- ___ Python tracker

[issue8587] test_import.py test failures on Py3K Mac OS X

Michael Foord added the comment: This is likely related to issue 8586 - the actual failure is very similar (a bad path in support.py). -- ___ Python tracker ___

[issue8587] test_import.py test failures on Py3K Mac OS X

New submission from Michael Foord : I get the following failures with test_import on Mac OS X 10.6.3: == ERROR: test_import (test.test_import.ImportTests) -- T

[issue8586] test_imp.py test failures on Py3K Mac OS X

New submission from Michael Foord : I get the following failure running test_imp on py3k, Mac OS X 10.6.3. == ERROR: test_package___file__ (__main__.PEP3147Tests)

[issue8576] test_support.find_unused_port can cause socket conflicts on Windows

Paul Moore added the comment: Here's a patch for test_logging. It needed a minor tweak to logging.config - but I can't see anywhere that this affects the documentation, so I didn't do a doc patch. I hope that's OK. I'll have a look at test_socket but that looks a bit too deep for me. And tes

[issue4388] test_cmd_line fails on MacOS X

Michael Foord added the comment: I still see this failure on Python 3 trunk with Mac OS X 10.6. -- nosy: +michael.foord ___ Python tracker ___ ___

[issue8581] Logging handlers do not handle double-closing very well

Vinay Sajip added the comment: - Original Message > From: Santoso Wijaya > File-like objects handle multiple close() gracefully, silently > making the second and subsequent close() calls to an already closed I/O > object > do nothing. Why can't the same expectation be applied to lo

[issue8582] urllib.urlretrieve fails with ValueError: Invalid format string

Senthil Kumaran added the comment: Fixed in trunk: r80675 release26-maint: r80676 py3K: r80677 release31-maint:r80678 -- resolution: -> fixed stage: unit test needed -> committed/rejected status: open -> closed ___ Python tracker

[issue7724] setup.py ignores SDK root on OSX

Ronald Oussoren added the comment: I've cleaned up the patch and made it clearer that platforms other than OSX aren't affected by rewriting code like this: f = os.path.join(d, "db.h") if sys.platform == "darwin" and is_macosx_sdk_path(d): f = os.path.join(sysroot, d[1:], "db.h") The new ve

[issue8581] Logging handlers do not handle double-closing very well

Santoso Wijaya added the comment: File-like objects handle multiple close() gracefully, silently making the second and subsequent close() calls to an already closed I/O object do nothing. Why can't the same expectation be applied to logging handlers? -- status: pending -> open __

[issue1533] Bug in range() function for large values

Mark Dickinson added the comment: Alexander: range *does* still accept such arguments (in 2.7); just not floats: >>> from decimal import Decimal >>> range(Decimal(20), Decimal(20)) [] >>> range(Decimal('1e100'), Decimal('1e100')) Traceback (most recent call last): File "", line 1, in TypeEr

[issue8581] Logging handlers do not handle double-closing very well

Vinay Sajip added the comment: This part of the code has been changed in trunk (to use weak references), and the error does not occur in Python 2.7/3.2. I'm not sure I fully agree with your assertion that it's not a programmer error to close a handler twice - this could certainly happen as a