[issue22628] Idle: Tree lines are spaced too close together.
Jean-Paul Calderone added the comment: This is still/again broken, probably because the "fixed" version still hard-codes all of the geometry values and these will certainly not be correct for all combinations of display dpi, font configuration, etc. Instead, `TreeNode.draw` and `TreeNode.drawtext` (at least) need to consider the size of the children and space them accordingly. -- nosy: +exarkun resolution: fixed -> status: closed -> open ___ Python tracker <https://bugs.python.org/issue22628> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34602] python3 resource.setrlimit strange behaviour under macOS
Jean-Paul Calderone added the comment: My understanding of the resolution of this ticket is that it is still not possible to use setrlimit with RLIMIT_STACK to raise the soft stack limit. Is that correct? In that case, the original bug report still seems valid and unresolved (and indeed, I am porting a project from Python 2.7 to Python 3.9 and on macOS it fails because it cannot raise the stack limit). -- nosy: +exarkun ___ Python tracker <https://bugs.python.org/issue34602> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6731] Add option of non-zero exit status of setup.py when building of extensions has failed
Changes by Jean-Paul Calderone : -- nosy: -Jean-Paul Calderone, exarkun ___ Python tracker <http://bugs.python.org/issue6731> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6731] Add option of non-zero exit status of setup.py when building of extensions has failed
Jean-Paul Calderone added the comment: It's only been six years, no need to rush. -- nosy: +Jean-Paul Calderone ___ Python tracker <http://bugs.python.org/issue6731> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5305] imaplib should support international mailbox names
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue5305> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21327] socket.type value changes after using settimeout()
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue21327> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6555] distutils config file should have the same name on both platforms and all scopes
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue6555> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18629] future division breaks timedelta division by integer
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue18629> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6377] distutils compiler switch ignored
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue6377> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20718] OpenBSD/AIX: tests passing a file descriptor with sendmsg/recvmsg failures
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue20718> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue20669] OpenBSD: socket.recvmsg tests fail with OSError: [Errno 40] Message too long
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue20669> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15945] memoryview + bytes fails
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue15945> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1103213] Adding the missing socket.recvall() method
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue1103213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5305] imaplib should support international mailbox names
Jean-Paul Calderone added the comment: > the twisted imap API is problematic for imaplib because twisted seems to > expect its arguments to already be Python unicode. Could you elaborate on this? As far as I can tell, it works fine: >>> import twisted.mail.imap4 >>> print u"Hello, \N{SNOWMAN}".encode('imap4-utf-7') Hello, &JgM- >>> print b'Hello, &JgM-'.decode('imap4-utf-7') Hello, ☃ >>> What would you expect to work differently? -- ___ Python tracker <http://bugs.python.org/issue5305> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21965] Add support for Memory BIO to _ssl
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue21965> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21965] Add support for Memory BIO to _ssl
Jean-Paul Calderone added the comment: Please do *not* add me to the nosy list of any issues. -- ___ Python tracker <http://bugs.python.org/issue21965> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12600] Add example of using load_tests to parameterise Test Cases
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue12600> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10721] Remove HTTP 0.9 server support
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue10721> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4887] environment inspection and manipulation API is buggy, inconsistent with "Python philosophy" for wrapping native APIs
Jean-Paul Calderone added the comment: What are the chances a future Python 2.x release will include any fix developed for this issue? -- ___ Python tracker <http://bugs.python.org/issue4887> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21652] Python 2.7.7 regression in mimetypes module on Windows
Jean-Paul Calderone added the comment: > That commit was fixing an existing problem; perhaps not your problem, but > someone's. To revert it would simply move the pain around. Doesn't the very same logic apply to the original commit? > I hope to be able to work on this fairly soon. Thanks. Much appreciated. -- ___ Python tracker <http://bugs.python.org/issue21652> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9291] mimetypes initialization fails on Windows because of non-Latin characters in registry
Jean-Paul Calderone added the comment: Please see http://bugs.python.org/issue21652 for a regression introduced by this change. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue9291> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21652] Python 2.7.7 regression in mimetypes module on Windows
Changes by Jean-Paul Calderone : -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue21652> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2506] Add mechanism to disable optimizations
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue2506> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4928] Problem with tempfile.NamedTemporaryFile
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue4928> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4999] multiprocessing.Queue does not order objects
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue4999> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1218234] inspect.getsource doesn't update when a module is reloaded
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue1218234> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21408] delegation of `!=` to the right-hand side argument is not always done
New submission from Jean-Paul Calderone: $ ~/Projects/cpython/3.4/python -c ' class Foo(object): def __ne__(self, other): return "yup" def __eq__(self, other): return "nope" class Bar(object): pass print(object() != Foo(), object() == Foo()) print(Bar() != Foo(), Bar() == Foo()) ' yup nope False nope $ The output I would expect from this is yup nope yup nope That is, even when the type of the left-hand argument is not a base class of the type of the right-hand argument, delegation to the right-hand argument is sensible if the left-hand argument does not implement the comparison. Note that the output also demonstrates that this is already the behavior for `==`. Only `!=` seems to suffer from this issue. -- components: Interpreter Core messages: 217699 nosy: exarkun priority: normal severity: normal status: open title: delegation of `!=` to the right-hand side argument is not always done type: behavior versions: Python 3.3, Python 3.4 ___ Python tracker <http://bugs.python.org/issue21408> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18629] future division breaks timedelta division by integer
Jean-Paul Calderone added the comment: > I think that's a very obscure interpretation of floor division for timedeltas :-) Note - I don't care about this. I just want `timedelta / int` to do the same thing in Python 2.7 with __future__.division as `timedelta / int` does in Python 3. Please don't reject this because of some unrelated discussion about how floor division should be implemented for timedelta. -- ___ Python tracker <http://bugs.python.org/issue18629> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11798] Test cases not garbage collected after run
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue11798> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18629] future division breaks timedelta division by integer
Jean-Paul Calderone added the comment: Hm. Maybe I am. Yet isn't true division implemented for this pair of types in Python 3? I'm not sure why it shouldn't be implemented for them in Python 2. Also that raises another question. Does a result of one and one half seconds make sense as the result of a floor division operation? -- ___ Python tracker <http://bugs.python.org/issue18629> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18629] future division breaks timedelta division by integer
New submission from Jean-Paul Calderone: datetime.timedelta instances are divisible by integers on Python 2.7, but not when __future__.division has been turned on: exarkun@top:~$ ~/Projects/cpython/2.7/python -c ' from datetime import timedelta print timedelta(seconds=3) / 2 ' 0:00:01.50 exarkun@top:~$ ~/Projects/cpython/2.7/python -c ' from __future__ import division from datetime import timedelta print timedelta(seconds=3) / 2 ' Traceback (most recent call last): File "", line 4, in TypeError: unsupported operand type(s) for /: 'datetime.timedelta' and 'int' exarkun@top:~$ ~/Projects/cpython/2.7/python Python 2.7.5+ (2.7:8205e72b5cfc, Aug 2 2013, 11:12:04) This presents a minor barrier to Python 3 transitions, since it prevents the use of __future__.division in a module trying to retain Python 2 compatibility where timedelta division is used. -- components: Library (Lib) messages: 194181 nosy: exarkun priority: normal severity: normal status: open title: future division breaks timedelta division by integer type: behavior versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue18629> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17134] Use Windows' certificate store for CA certs
Jean-Paul Calderone added the comment: > Sounds promising. Do you think this should be hooked into > SSLContext.set_default_verify_paths, or be exposed as a separate method? If there were an API which exposed the certificate material, then this would be more useful to libraries trying to do other things (present debugging information, use an alternate SSL implementation *wink*, etc). If this is *only* wrapped up inside set_default_verify_paths then many of these extra things are impossible with a seconding binding to the same API. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue17134> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16195] Difficult or impossible to figure out how garbage collector and weak references should interact for user-defined extension types
New submission from Jean-Paul Calderone: There appears to be very little, if any, documentation about how to handle the list at tp_weaklistoffset for types supporting being weak referenced, particularly with respect to garbage collection. Who owns the list? Who owns the objects in the list? Should the list be traversed by the extension type's tp_traverse? Should it ever be INCREF'd or DECREF'd? Does tp_dealloc have any responsibilities with respect to it? >From looking at CPython's own source, it appears that tp_traverse should not >touch it (Yhg1s confirmed this on #python). Cython, at least, appears to have >come to an alternate conclusion though - it generates tp_traverse functions >which visit the list (and provoke gc assertions to fail on Python 2.7 in debug >mode). Some documentation about what is correct to do would be excellent, and would make it easier to explain to Cython developers what they're doing wrong (or confirm that they're doing something right, in which case there are some more bugs to file against the CPython stdlib, since they do something different from Cython). -- assignee: docs@python components: Documentation messages: 172639 nosy: docs@python, exarkun priority: normal severity: normal status: open title: Difficult or impossible to figure out how garbage collector and weak references should interact for user-defined extension types ___ Python tracker <http://bugs.python.org/issue16195> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3982] support .format for bytes
Jean-Paul Calderone added the comment: > The development cost and maintenance cost is surely part of the evaluation > when deciding whether to implement a feature, no? Sure, but in an open source project where almost all contributions are done by volunteers (ie, donated), what is the development cost? -- ___ Python tracker <http://bugs.python.org/issue3982> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3982] support .format for bytes
Jean-Paul Calderone added the comment: > The price of maintaining exceeds the potential very limited benefits from the > use. The "very limited benefits" of being able to write I/O code without roughly 3 times code bloat? Perhaps for people who don't write code that does non-trivial I/O, but for the rest of us the benefits are pretty significant. > I suspect, but have not verified, that having a bytes version of this code > would now require an implementation that shared very little with the str > version. The implementation may be difficult, therefore no one should attempt it? -- ___ Python tracker <http://bugs.python.org/issue3982> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3982] support .format for bytes
Jean-Paul Calderone added the comment: Since Benjamin originally requested this feature, and then decided that he could accomplish his desired goal (ftplib porting, as far as I can tell) without it, I think that the "rejected" status is actually incorrect. I think that Benjamin just wanted to indicate that he no longer needed the feature. This doesn't mean that no one else will need the feature, and as it turns out the comments seem to reveal that other people do need the feature (also, I need the feature). So, adjusting the ticket metadata to reflect that this is a valid feature request just waiting for someone to implement it, not a rejected idea that is not welcome in Python. -- nosy: +exarkun resolution: rejected -> status: closed -> open ___ Python tracker <http://bugs.python.org/issue3982> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15945] memoryview + bytes fails
Jean-Paul Calderone added the comment: > What is the expected outcome? memoryviews can't be resized, so this scenario isn't possible: The same as `view.tobytes() + bytes`, but without the extra copy implied by `view.tobytes()`. > Just prepend the empty bytestring if you want to make sure the result is a > bytes object: Or I could explicitly convert the memoryview to a bytes object. That strikes me as rather preferable. However, this defeats one use of memoryview, which is to avoid unnecessary copying. So it might be suitable workaround for some cases, but not all. -- ___ Python tracker <http://bugs.python.org/issue15945> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15945] memoryview + bytes fails
New submission from Jean-Paul Calderone: Python 3.3.0rc2+ (default:9def2209a839, Sep 10 2012, 08:44:51) [GCC 4.6.3] on linux Type "help", "copyright", "credits" or "license" for more information. >>> memoryview(b'foo') + b'bar' Traceback (most recent call last): File "", line 1, in TypeError: unsupported operand type(s) for +: 'memoryview' and 'bytes' >>> b'bar' + memoryview(b'foo') b'barfoo' >>> -- messages: 170511 nosy: exarkun priority: normal severity: normal status: open title: memoryview + bytes fails type: behavior versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue15945> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15912] Intermittent import failure
New submission from Jean-Paul Calderone: The attached unit test fails with an ImportError... sometimes. Here's a little blob of shell that seems to make the failure come up more quickly: while ~/Projects/cpython/3.3/python -m unittest -v test_broken_import; do rm -rf test_broken_import; rm -rf __pycache__/; done An example of the output when I run it: exarkun@top:/tmp$ while ~/Projects/cpython/3.3/python -m unittest -v test_broken_import_minimal; do rm -rf test_broken_import; rm -rf __pycache__/; done test_renamedSource (test_broken_import_minimal.BrokenTests) ... ok -- Ran 1 test in 0.004s OK test_renamedSource (test_broken_import_minimal.BrokenTests) ... ok -- Ran 1 test in 0.005s OK test_renamedSource (test_broken_import_minimal.BrokenTests) ... > /tmp/test_broken_import_minimal.py(53)test_renamedSource() -> print(e) (Pdb) c No module named 'twisted_renamed_helper' ERROR == ERROR: test_renamedSource (test_broken_import_minimal.BrokenTests) -- Traceback (most recent call last): File "./test_broken_import_minimal.py", line 50, in test_renamedSource from twisted_renamed_helper import module ImportError: No module named 'twisted_renamed_helper' -- Ran 1 test in 0.759s FAILED (errors=1) -- components: Interpreter Core files: test_broken_import_minimal.py messages: 170225 nosy: exarkun priority: normal severity: normal status: open title: Intermittent import failure versions: Python 3.3 Added file: http://bugs.python.org/file27168/test_broken_import_minimal.py ___ Python tracker <http://bugs.python.org/issue15912> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue15911] Debugging import problems is hard
New submission from Jean-Paul Calderone: Debugging problems involving the frozen importlib._bootstrap is difficult, because the source for importlib._bootstrap is not available to pdb. The bootstrap code can be stepped through, but with only function names and line numbers available, not source lines. The value of having importlib written in Python would be greatly enhanced if it were more like a regular Python module that, eg, pdb could display source lines from. -- components: Interpreter Core, Library (Lib) messages: 170221 nosy: exarkun priority: normal severity: normal status: open title: Debugging import problems is hard versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue15911> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14325] Stop using the garbage collector to manage the lifetime of the getargs.c freelist
Jean-Paul Calderone added the comment: If it's a bit faster, that'd be a nice win, but I didn't benchmark. I'm primarily interested in correctness in the PyPy case (PyPy re-uses this code), and I think CPython benefits from the slightly simplified code as well. If you do any benchmarks, I'd love to hear the results, though. :) -- ___ Python tracker <http://bugs.python.org/issue14325> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14325] Stop using the garbage collector to manage the lifetime of the getargs.c freelist
Changes by Jean-Paul Calderone : -- resolution: -> fixed status: open -> closed ___ Python tracker <http://bugs.python.org/issue14325> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14325] Stop using the garbage collector to manage the lifetime of the getargs.c freelist
Changes by Jean-Paul Calderone : -- keywords: +patch Added file: http://bugs.python.org/file24873/getargs.patch ___ Python tracker <http://bugs.python.org/issue14325> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14325] Stop using the garbage collector to manage the lifetime of the getargs.c freelist
New submission from Jean-Paul Calderone : Allocating a Python list and a bunch of Capsules for each PyArg_ParseTuple call is expensive and unnecessarily complicated. The freelist never escapes getargs.c (if it ever did, it would be a bug). The same job can be accomplished with a normal C array. -- assignee: exarkun messages: 155926 nosy: exarkun priority: normal severity: normal status: open title: Stop using the garbage collector to manage the lifetime of the getargs.c freelist type: enhancement ___ Python tracker <http://bugs.python.org/issue14325> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1531415] parsetok.c emits warnings by writing to stderr
Jean-Paul Calderone added the comment: > May somebody check for this? Otherwise the bug could be considered invalid. This is not the proper workflow for bug tracking. "No one is working on this right now" is not the same as "This bug is invalid". No one worked on this ticket almost *seven years* after I filed it. The "invalid" state in the issue tracker is for issues that have been filed that *do not describe a bug that exists at all* (or a feature is being rejected as a bad idea or something that will otherwise not be added to Python and will not be implemented). Please do not close tickets as invalid just because no one is working on resolving them *right now*. The purpose of closing issues is to keep track of useful development that is happening. In and of itself, closing issues is a useless activity; it is only useful inasmuch as it reflects useful development. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue1531415> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13556] When tzinfo.utcoffset is out-of-bounds, the exception message is misleading
New submission from Jean-Paul Calderone : When a timezone produces an out-of-bounds utc offset, the resulting exception always claims that the offset was 1440, rather than whatever it was. Example: from datetime import timedelta, datetime, tzinfo class X(tzinfo): def utcoffset(self, time): return timedelta(days=2) datetime.now(tz=X()) -- components: Library (Lib) messages: 149046 nosy: exarkun priority: normal severity: normal status: open title: When tzinfo.utcoffset is out-of-bounds, the exception message is misleading type: behavior versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue13556> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12944] Accept arbitrary files for packaging's upload command
Jean-Paul Calderone added the comment: > pysetup run upload -f dist/spam-0.2.tar.gz -f dist/spam-0.2.exe I'm not sure why it's "run upload" instead of just "upload", but maybe that's the convention in pysetup. Apart from that, this looks like a vast improvement to me. As far as not supporting globs goes, I guess I don't really care either way. If globs aren't supported, then I'll probably end up globbing somewhere else (or constructing the full upload list in some other automated way). The motivation for the complaint is that too many things require manual interaction; I'm not going to use a new, easily automated utility manually. :) -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue12944> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11657] multiprocessing_{send,recv}fd fail with fds > 256
Jean-Paul Calderone added the comment: Thanks for the patch Petri. Are you interested in writing a unit test for this as well? -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue11657> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2506] Line tracing of continue after always-taken if is incorrect
Jean-Paul Calderone added the comment: Since the main argument for not fixing this bug seems to be that it doesn't affect many users, it seems like I should comment here that the issue is affecting me. A recently proposed addition to Twisted gets bitten by this case, resulting in a report of less than full test coverage when in fact the tests do exercise every line and branch of the change. Perhaps it is too hard to add and maintain a no-optimizations feature for Python (although I agree with Ned that this would be a useful feature for many reasons, not just to fix this bug). There are other possible solutions to the issue of inaccurate coverage reports though. For example, Python could provide an API for determining which lines have code that might be executed. coverage.py (and the stdlib trace.py) currently use the code object's lnotab to decide which lines might be executable. Maybe that should omit "continue" lines that get jumped over. If the line will never execute, it seems there is no need to have it in the lnotab. Using the lnotab is something of a hack though, so it might also make sense to leave it alone but introduce an API to get the same information, but corrected for whatever peephole optimizations the interpreter happens to have. As far as the "not a bug" arguments go, I don't think it matters much whether you ultimately decide to call it a bug or a feature request. It *is* clearly a useful feature to some people though, and rejecting the requested behavior as "not a bug" doesn't help anyone. So call it a feature request if that makes it more palletable. :) -- nosy: +exarkun resolution: wont fix -> status: closed -> open ___ Python tracker <http://bugs.python.org/issue2506> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12443] locale.setlocale(locale.LC_ALL, locale.getlocale()) fails for some locales
New submission from Jean-Paul Calderone : Consider this transcript from OS X 10.6: >>> import locale >>> locale.getlocale() (None, None) >>> locale.setlocale(locale.LC_ALL, _) 'C' >>> locale.setlocale(locale.LC_ALL, 'en_US.UTF-8') 'en_US.UTF-8' >>> locale.getlocale() ('en_US', 'UTF8') >>> locale.setlocale(locale.LC_ALL, _) Traceback (most recent call last): File "", line 1, in File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/locale.py", line 494, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting >>> OS X does not recognize 'en_US.UTF8', only 'en_US.UTF-8'. However, when passed a tuple, the locale module tries to normalize the values. It ends up turning the result of getlocale from ('en_US', 'UTF-8') into 'en_US.UTF8'. -- assignee: ronaldoussoren components: Extension Modules, Library (Lib), Macintosh messages: 139445 nosy: exarkun, ronaldoussoren priority: normal severity: normal status: open title: locale.setlocale(locale.LC_ALL, locale.getlocale()) fails for some locales type: behavior versions: Python 2.6, Python 2.7 ___ Python tracker <http://bugs.python.org/issue12443> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12126] incorrect select documentation
New submission from Jean-Paul Calderone : http://docs.python.org/py3k/howto/sockets.html#non-blocking-sockets "And if you put a socket in more than one input list, it will only be (at most) in one output list." >>> import socket >>> s = socket.socket() >>> s.connect(('localhost', 22)) >>> import select >>> select.select([s], [s], []) ([], [], []) >>> -- assignee: docs@python components: Documentation messages: 136350 nosy: docs@python, exarkun priority: normal severity: normal status: open title: incorrect select documentation type: behavior ___ Python tracker <http://bugs.python.org/issue12126> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11798] Test cases not garbage collected after run
Jean-Paul Calderone added the comment: Here's Trial's implementation: http://twistedmatrix.com/trac/browser/trunk/twisted/trial/runner.py#L138 -- ___ Python tracker <http://bugs.python.org/issue11798> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11798] Test cases not garbage collected after run
Jean-Paul Calderone added the comment: > I thought unittest was just handed a bunch of TestCase instances and couldn't > do much about insuring they were garbage collected. True. But unittest could ensure that it doesn't keep a reference to each TestCase instance after it finishes running it. Then, if no one else has a reference either, it can be garbage collected. -- ___ Python tracker <http://bugs.python.org/issue11798> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11798] Test cases not garbage collected after run
Jean-Paul Calderone added the comment: Trial lets test cases get garbaged collected. When we noticed this wasn't happening, we treated it as a bug and fixed it. No one ever complained about the change. I don't see any obvious way in which an application would even be able to tell the difference (a user can tell the difference by looking at top). In what case do you think this change would result in broken application code? -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue11798> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10935] wsgiref.handlers.BaseHandler and subclasses of str
Jean-Paul Calderone added the comment: > Phillip, your argument about interfacing with code written in C doesn't work > for built-in immutable types like str. Sure it does. Definitely-str is easier to handle in C than maybe-str-subclass. It doesn't matter that str.__new__ gets called. Other things might get called too, with who-knows-what side-effects. wsgi is right to demand str and only str and exactly str. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue10935> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10661] ElementTree QName has a very uninformative repr()
New submission from Jean-Paul Calderone : This is somewhat unfortunate behavior: >>> from xml.etree.ElementTree import QName >>> QName('foo') >>> It becomes even more apparent when encountered in a situation like this: >>> print {QName('foo'): 'bar', QName('baz'): 'quux'} {: 'bar', : 'quux'} >>> I would like to see QName.__repr__ return something like '' % (text,) -- messages: 123687 nosy: exarkun priority: normal severity: normal status: open title: ElementTree QName has a very uninformative repr() type: behavior ___ Python tracker <http://bugs.python.org/issue10661> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10377] cProfile incorrectly labels its output
New submission from Jean-Paul Calderone : Consider this transcript: >>> cProfile.run("import time; time.sleep(1)") 4 function calls in 1.012 CPU seconds Ordered by: standard name ncalls tottime percall cumtime percall filename:lineno(function) 10.0110.0111.0121.012 :1() 10.0000.0001.0121.012 {built-in method exec} 11.0011.0011.0011.001 {built-in method sleep} 10.0000.0000.0000.000 {method 'disable' of '_lsprof.Profiler' objects} >>> It is not the case that the profiled code uses >1 CPU seconds. It spends the entire time sleeping. The default timer for cProfile is a wallclock timer. The output should reflect this. -- messages: 120890 nosy: exarkun priority: normal severity: normal status: open title: cProfile incorrectly labels its output type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker <http://bugs.python.org/issue10377> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10169] socket.sendto raises incorrect exception when passed incorrect types
New submission from Jean-Paul Calderone : >>> s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) >>> s.bind(('', 0)) >>> s.sendto(u'hellé', s.getsockname()) Traceback (most recent call last): File "", line 1, in TypeError: sendto() takes exactly 3 arguments (2 given) >>> s.sendto(3, s.getsockname()) Traceback (most recent call last): File "", line 1, in TypeError: sendto() takes exactly 3 arguments (2 given) >>> s.sendto('hello', s.getsockname()) 5 The TypeError gives the wrong explanation for what's wrong. -- components: Library (Lib) messages: 119320 nosy: exarkun priority: normal severity: normal status: open title: socket.sendto raises incorrect exception when passed incorrect types type: behavior versions: Python 2.6, Python 2.7, Python 3.2 ___ Python tracker <http://bugs.python.org/issue10169> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10093] Warn when files are not explicitly closed
Jean-Paul Calderone added the comment: If the warnings are emitted as usual with the warnings module, you can use -W to control this. -X isn't necessary. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue10093> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9994] Python becoming orphaned over ssh
Jean-Paul Calderone added the comment: fwiw http://mail.python.org/pipermail/python-list/2010-September/1256545.html -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue9994> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9966] platform : a boolean to know easily when a system is posix
Jean-Paul Calderone added the comment: It could, but why introduce this redundancy with `os.name`? -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue9966> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9961] Identity Crisis! variable assignment using strftime fails comparison test.
Jean-Paul Calderone added the comment: You mistakenly used "is" for these comparisons, rather than "==". The strftime involvement is a red herring. The real problem is the use of an /identity/ comparison rather than an /equality/ comparison. -- nosy: +exarkun resolution: -> invalid status: open -> closed ___ Python tracker <http://bugs.python.org/issue9961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9953] 2 scripts running from crontab simultaneously reference the same instance of a variable
Jean-Paul Calderone added the comment: You can't rely on id() to return distinct values across different processes. It guarantees uniqueness *within a single process* (at any particular moment). In other words, you're misusing id() here. This is not a Python bug. -- nosy: +exarkun resolution: -> invalid status: open -> closed ___ Python tracker <http://bugs.python.org/issue9953> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9090] Error code 10035 calling socket.recv() on a socket with a timeout (WSAEWOULDBLOCK - A non-blocking socket operation could not be completed immediately)
Jean-Paul Calderone added the comment: > Unfortunately, select doesn't necessarily update the timeout variable with > the remaining time, so we can't rely on this. This would mean having the > select enclosed within gettimeofday and friends, which seems a bit overkill... How is it "overkill" to be correct? -- ___ Python tracker <http://bugs.python.org/issue9090> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8998] add crypto routines to stdlib
Jean-Paul Calderone added the comment: > I should note that I can't touch anything to do with Elliptic Curve crypto. > I don't know if I can comment on the reasons for that. Hopefully anything ECC related can be done separately. There's certainly no ECC APIs in Python now, so there would be no loss of functionality if any new crypto-related APIs didn't include ECC. Later if someone is sufficiently interesting, they could add it to the base library. -- ___ Python tracker <http://bugs.python.org/issue8998> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8998] add crypto routines to stdlib
Jean-Paul Calderone added the comment: What it will bring: APIs which aren't absolutely insane; full SSL support; RSA, DSA, ECDSA, Diffie-Hellman, EC Diffie-Hellman, AES, Triple DES, DES, RC2, RC4, SHA-1, SHA-256, SHA-384, SHA-512, MD2, MD5, HMAC: Common cryptographic algorithms used in public-key and symmetric-key cryptography; simplified FIPS 140 validation; better licensing (MPL). I'm interested in stuff based on nss, but I definitely won't promise to do the work. Fortunately dmalcolm seems to be on top of that. :) -- ___ Python tracker <http://bugs.python.org/issue8998> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8998] add crypto routines to stdlib
Jean-Paul Calderone added the comment: How about nss? As a bonus, this would also avoid making more work for Fedora (<http://fedoraproject.org/wiki/FedoraCryptoConsolidation>). -- ___ Python tracker <http://bugs.python.org/issue8998> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9875] Garbage output when running setup.py on Windows
Jean-Paul Calderone added the comment: This seems to have been caused by an ill-placed distutils.log.set_verbosity(3) call. With that removed, this output isn't generated by default. So perhaps this is invalid, feel free to close it as so if you agree. -- ___ Python tracker <http://bugs.python.org/issue9875> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9881] PySSL_SSLread loops until data is available, even in non-blocking mode
Jean-Paul Calderone added the comment: Hm. I must have been testing with old versions, since I can't reproduce this now. Sorry for the noise. -- resolution: out of date -> duplicate status: pending -> closed ___ Python tracker <http://bugs.python.org/issue9881> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9881] PySSL_SSLread loops until data is available, even in non-blocking mode
Changes by Jean-Paul Calderone : -- title: PySSL_SSLRead loops until data is available, even in non-blocking mode -> PySSL_SSLread loops until data is available, even in non-blocking mode ___ Python tracker <http://bugs.python.org/issue9881> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9881] PySSL_SSLRead loops until data is available, even in non-blocking mode
New submission from Jean-Paul Calderone : Here's a transcript which demonstrates the blocking behavior: >>> import socket >>> import time >>> import ssl >>> s = ssl.wrap_socket(socket.socket()) >>> s.connect(('localhost', 8443)) >>> s.send('GET /async.rpy HTTP/1.1\r\n\r\n') 27 >>> s.setblocking(False) >>> a = time.time(); s.recv(1024); b = time.time() 'HTTP/1.1 200 OK\r\nTransfer-Encoding: chunked\r\nDate: Thu, 02 Sep 2010 11:51:03 GMT\r\nContent-Type: text/html\r\nServer: TwistedWeb/10.1.0+r29954\r\n\r\n4c\r\nSorry to keep you waiting.\r\n0\r\n\r\n' >>> print b - a 4.13403391838 >>> (This can be reproduced using any web server which is a bit slow in responding; it's very obvious here because I used a server that intentionally waits several seconds before generating a response). -- components: Library (Lib) messages: 116629 nosy: exarkun priority: normal severity: normal status: open title: PySSL_SSLRead loops until data is available, even in non-blocking mode versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2, Python 3.3 ___ Python tracker <http://bugs.python.org/issue9881> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9875] Garbage output when running setup.py on Windows
New submission from Jean-Paul Calderone : The output of setup.py is polluted with this log message: Importing new compiler from distutils.msvc9compiler on Windows. For example, using pyOpenSSL's setup.py, running "setup.py --version" produces this output: Importing new compiler from distutils.msvc9compiler 0.10 But the version number of pyOpenSSL is "0.10", not "Importing new compiler from distutils.msvc9compiler\n0.10". The --quiet flag does not solve this problem, apparently because this log message is done at the top-level of msvccompiler.py, perhaps before --quiet is interpreted. This interferes with my build automation which depends on "setup.py --version" producing the version number of the project in order to properly compute certain filenames. -- assignee: tarek components: Distutils messages: 116552 nosy: eric.araujo, exarkun, tarek priority: normal severity: normal status: open title: Garbage output when running setup.py on Windows type: behavior versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue9875> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8685] set(range(100000)).difference(set()) is slow
Changes by Jean-Paul Calderone : -- nosy: -exarkun ___ Python tracker <http://bugs.python.org/issue8685> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8685] set(range(100000)).difference(set()) is slow
Jean-Paul Calderone added the comment: > I'll be looking at it shortly. Py3.2 is still aways from release so there is > no hurry. I would consider reviewing and possibly apply this change, but I don't want to invade anyone's territory. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue8685> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9053] distutils compiles extensions so that Python.h cannot be found
Changes by Jean-Paul Calderone : -- resolution: -> fixed status: open -> closed ___ Python tracker <http://bugs.python.org/issue9053> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9053] distutils compiles extensions so that Python.h cannot be found
Jean-Paul Calderone added the comment: exar...@boson:~/Projects/python-signalfd/trunk$ PYTHONPATH= ~/Projects/python/branches/py3k/python setup.py build_ext -i running build_ext building 'signalfd._signalfd' extension creating build creating build/temp.linux-i686-3.2 creating build/temp.linux-i686-3.2/signalfd gcc -pthread -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/exarkun/Projects/python/branches/py3k/Include -I/home/exarkun/Projects/python/branches/py3k -c signalfd/_signalfd.c -o build/temp.linux-i686-3.2/signalfd/_signalfd.o gcc -pthread -shared build/temp.linux-i686-3.2/signalfd/_signalfd.o -o /home/exarkun/Projects/python-signalfd/trunk/signalfd/_signalfd.so exar...@boson:~/Projects/python-signalfd/trunk$ -- ___ Python tracker <http://bugs.python.org/issue9053> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9276] pickle should support methods
Jean-Paul Calderone added the comment: > Note, however that since unbound methods have been removed in 3.x, it is not > trivial to find a fully qualified name of a method anymore. This is a rather sad loss of functionality. -- ___ Python tracker <http://bugs.python.org/issue9276> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9276] pickle should support methods
Jean-Paul Calderone added the comment: > I also like Antoine's idea of pickling the function/method name instead of > the whole code object. I like it too. That's why I suggested it in the first comment on the ticket (read the linked code). I guess Alexander likes it too, since he basically said as much in the second comment. ;) -- ___ Python tracker <http://bugs.python.org/issue9276> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9276] pickle should support methods
Jean-Paul Calderone added the comment: For example: exar...@boson:~$ python Python 2.6.4 (r264:75706, Dec 7 2009, 18:45:15) [GCC 4.4.1] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> class x(object): ... def __reduce__(self): ... import os ... return os.system, ('echo "Hello from sploitland"',) ... >>> import pickle >>> pickle.loads(pickle.dumps(x())) Hello from sploitland 0 >>> -- ___ Python tracker <http://bugs.python.org/issue9276> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9276] pickle should support methods
Jean-Paul Calderone added the comment: > By adding default support for unpickling code objects, you can trick the unpickling code into executing serialized code: This doesn't sound correct to me. You can *already* trick unpickling code into executing serialized code. You don't need this feature in order to be able to do it. -- ___ Python tracker <http://bugs.python.org/issue9276> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9276] pickle should support methods
Jean-Paul Calderone added the comment: > This is a security feature and should not be broken ! Can you explain this? I don't think I agree, since an attacker can always serialize whatever they feel like. It's the person doing the deserialization that has to be careful. -- ___ Python tracker <http://bugs.python.org/issue9276> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2124] xml.sax and xml.dom fetch DTDs by default
Jean-Paul Calderone added the comment: Yes. -- ___ Python tracker <http://bugs.python.org/issue2124> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9276] pickle should support methods
New submission from Jean-Paul Calderone : pickle doesn't support methods: >>> class x: ... def y(self): ... pass ... >>> import pickle >>> pickle.dumps(x.y) Traceback (most recent call last): File "", line 1, in File "/home/exarkun/Projects/python/branches/py3k/Lib/pickle.py", line 1314, in dumps Pickler(f, protocol, fix_imports=fix_imports).dump(obj) _pickle.PicklingError: Can't pickle : attribute lookup builtins.function failed It would be easy to fix this, though. Here's a link to some code that implements it: http://twistedmatrix.com/trac/browser/trunk/twisted/persisted/styles.py?rev=1 -- components: Library (Lib) messages: 110473 nosy: exarkun priority: normal severity: normal status: open title: pickle should support methods type: feature request ___ Python tracker <http://bugs.python.org/issue9276> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1218234] inspect.getsource doesn't update when a module is reloaded
Jean-Paul Calderone added the comment: > linecache.checkcache does a stat() of every single cached file. Ah, sorry. I didn't read carefully enough. I see that the patch passes in the filename and checkcache restricts the work it does in that case. Something else to consider, though, is that this change means you'll also get the new source if you *don't* reload the module, too. So, what exactly is inspect.getsource() supposed to be doing? Giving you the current on-disk contents of the relevant source file? Or giving you the actual source corresponding to the object passed to it? If the latter, then this actually needs to be more tightly integrated with module reloading somehow. -- ___ Python tracker <http://bugs.python.org/issue1218234> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1218234] inspect.getsource doesn't update when a module is reloaded
Jean-Paul Calderone added the comment: Calling linecache.checkcache for every inspect.getsource call sounds like a fairly bad idea to me. linecache.checkcache does a stat() of every single cached file. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue1218234> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5286] urrlib2 digest authentication problems
Jean-Paul Calderone added the comment: Some unit tests which demonstrate the present non-working behavior and the correctness of the fix would help a lot. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue5286> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4928] Problem with tempfile.NamedTemporaryFile
Jean-Paul Calderone added the comment: I can't think of any way that you might be able to implement the behavior being requested here. Instead, if you don't want to leave files lying around, use TemporaryFile instead of NamedTemporaryFile. Perhaps the documentation for NamedTemporary file could be updated to explain this limitation, though. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue4928> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9127] subprocess.Popen.communicate() and SIGCHLD handlers
Jean-Paul Calderone added the comment: You should include all relevant issue materials here, in the Python issue tracker. This ticket will be useless as soon as pastie.org decides to forget about your paste. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue9127> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9080] Provide list prepend method (even though it's not efficient)
Jean-Paul Calderone added the comment: > The argument that "there are already two ways to do it, so why add a third?", > is not bad, but if applied to appending, it would ban the append() method... > except that it's already there. Not quite. First let's consider the insert approach. Unlike with prepending, you first have to find the length of the list: L.insert(len(L), x). So it's no longer just a matter of an extra constant (although it /is/ still pretty simple). Next, the slice assignment solution: L[-1:] = [x] doesn't work, because it actually includes the last element of L in the slice, so it replaces the last value instead of appending the new element. So there's really just two ways, L.insert(len(L), x) and L.append(x). To me, it seems like the extra cognitive load of figuring out whether the parameter to L.insert should be len(L) or len(L) - 1 or len(L) + 1 makes L.append worthwhile. Maybe the same argument could be applied to L.insert(0, x), but it seems like a simpler case ("of _course_ inserting at 0 prepends") to me. The other cost of adding a new list method is updating all of the list-like interfaces out there to also provide this, although that would probably be a cost worth accepting for a really compelling new method. > Sorry to bring up this issue that I guess has been raised (many times?) > before, but I thought I'd have a stab at a convincing case! No need to apologize! Thanks for the reasoned argument. At least this can serve as a reference when the issue comes up again in the future, and perhaps someone else will be more convinced than overrule me. :) -- ___ Python tracker <http://bugs.python.org/issue9080> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9080] Provide list prepend method (even though it's not efficient)
Jean-Paul Calderone added the comment: Thanks for bringing this up. I think you have more work to do to successfully make the case that L.insert(0, x) is "difficult" enough to merit the addition of a new list method. There are already at least two in-place insert-at-front list APIs (the second being L[:0] = [x]). There should be a very compelling reason for adding a third, and I don't think that being able to skip the extra 0 in the L.insert version is going to suffice. -- nosy: +exarkun resolution: -> wont fix status: open -> closed ___ Python tracker <http://bugs.python.org/issue9080> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9053] distutils compiles extensions so that Python.h cannot be found
New submission from Jean-Paul Calderone : With a checkout of the py3k branch, building an extension module using distutils fails: error: Python.h: No such file or directory This is clearly because the wrong -I option is being supplied: gcc -pthread -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/exarkun/Projects/python-signalfd/trunk/Include -I/home/exarkun/Projects/python/branches/py3k -c signalfd/_signalfd.c -o build/temp.linux-i686-3.2/signalfd/_signalfd.o Building the extension with Python 3.1 all the way back through Python 2.3 does work, though. -- assignee: tarek components: Distutils messages: 108321 nosy: exarkun, tarek priority: critical severity: normal status: open title: distutils compiles extensions so that Python.h cannot be found versions: Python 3.1 ___ Python tracker <http://bugs.python.org/issue9053> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8524] SSL sockets do not retain the parent socket's attributes
Jean-Paul Calderone added the comment: It might be nice to see the version that avoids the dup() and has the duplicate code instead (interesting trade-off ;). Just for the sake of comparison against the forget() proposal. -- ___ Python tracker <http://bugs.python.org/issue8524> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1300] subprocess.list2cmdline doesn't do pipe symbols
Jean-Paul Calderone added the comment: It will return the former. To clarify, it's true that there appears to be a problem with Popen(['echo', 'foo|bar'], shell=True). That is being tracked in issue7839. What's invalid is the report that list2cmdline() should be quoting strings with | in them. list2cmdline() is documented as being an implementation of the quoting convention implemented by the MS C runtime. That quoting convention does not require | to be quoted. It's cmd.exe which requires | to be quoted (if it is to be part of an argument value, rather than to indicate a command pipeline of some sort). cmd.exe quoting rules need to be addressed separately from the MS C quoting rules used even if cmd.exe isn't involved. -- ___ Python tracker <http://bugs.python.org/issue1300> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1300] subprocess.list2cmdline doesn't do pipe symbols
Jean-Paul Calderone added the comment: See the commit message for r82075 and the discussion on issue8972 and issue7839. -- ___ Python tracker <http://bugs.python.org/issue1300> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1573931] WSGI, cgi.FieldStorage incompatibility
Jean-Paul Calderone added the comment: It's not terribly productive to block a fix for this specific issue in the WSGI specification on the big pile of contentious unrelated issues. It would make sense to issue a new WSGI specification with a correction for only this issue. The rest of the WSGI 1.1 issues can wait for a subsequent revision. Of course, actually getting this done involves either getting web-sig behind it or deciding to ignore web-sig and just do it. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue1573931> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8972] subprocess.list2cmdline doesn't quote the & character
Jean-Paul Calderone added the comment: I've reverted the issue1300 revision from 2.6, 2.7, 3.1, and 3.2. I hope 7839 is resolved soon. -- ___ Python tracker <http://bugs.python.org/issue8972> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1300] subprocess.list2cmdline doesn't do pipe symbols
Jean-Paul Calderone added the comment: I reverted r60115 from trunk (2.7) in r82075 and from py3k in r82076. -- nosy: +exarkun resolution: fixed -> invalid ___ Python tracker <http://bugs.python.org/issue1300> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9028] test_support.run_unittest cmdline options and arguments
Jean-Paul Calderone added the comment: These sound more like features for the unittest runner (one of which is implemented already). Also, please don't propagate "::" as a namespace separator in Python. That's what "." is for. -- nosy: +exarkun ___ Python tracker <http://bugs.python.org/issue9028> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8972] subprocess.list2cmdline doesn't quote the & character
Jean-Paul Calderone added the comment: > That remark is not relevant, because the actual problem is different. Maybe you can expand the test case to demonstrate the actual problem? The tests in the latest patch are for list2cmdline directly. But you can't observe the problem a bug in list2cmdline causes until you actually try to launch a child process. So perhaps the test should do that? -- ___ Python tracker <http://bugs.python.org/issue8972> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8972] subprocess.list2cmdline doesn't quote the & character
Jean-Paul Calderone added the comment: http://www.autohotkey.net/~deleyd/parameters/parameters.htm#WINCRULES is a helpful reference, by the way. -- ___ Python tracker <http://bugs.python.org/issue8972> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com