[issue19223] bz2 and 'x' mode open

Changes by Terry J. Reedy : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue19230] Reimplement the keyword module in C

New submission from STINNER Victor: To speedup Python startup, I propose to reimplement the keyword module in C. Attached patch implements it. * Remove Lib/keyword.py * Add Tools/scripts/keyword.py: script to build Modules/keyword.h * The new module is Modules/keyword.c I chose to change the k

[issue19227] test_multiprocessing_xxx hangs under Gentoo buildbots

R. David Murray added the comment: Here is a more useful traceback: [394] test_multiprocessing_spawn Timeout (1:00:00)! Thread 0xb76a16c0: File "/home/rdmurray/p34/Lib/multiprocessing/popen_fork.py", line 30 in poll File "/home/rdmurray/p34/Lib/multiprocessing/popen_fork.py", line 54 in wait

[issue19230] Reimplement the keyword module in C

STINNER Victor added the comment: I fail to see a difference with my patch in the startup time, but I see that the number of syscalls is reduced by 10 (558 => 548). -- ___ Python tracker __

[issue19230] Reimplement the keyword module in C

STINNER Victor added the comment: The patch adds 448 bytes to the stripped python executable file. -- ___ Python tracker ___ ___ Pytho

[issue19201] Add 'x' mode to lzma.open

Terry J. Reedy added the comment: The bug versus feature issue does not depend on whether the patch could cause a regression. (I think feature patches might actually be less likely than bug fixes to cause regressions, but it does not matter.) Nor is oversight, not adding a feature when it coul

[issue19227] test_multiprocessing_xxx hangs under Gentoo buildbots

STINNER Victor added the comment: See also issue #12413 which proposes to dump also the Python traceback of child processes to analyze multiprocessing issues. -- nosy: +neologix ___ Python tracker

[issue19227] test_multiprocessing_xxx hangs under Gentoo buildbots

R. David Murray added the comment: That's great, but without a patch it doesn't help me debug *this* failure :) Any suggestions for getting more information out of that test (I'm not familiar with multiprocessing...I'm already confused by the fact that the test is named test_multiprocessing_sp

[issue18891] Master patch for content manager addtion to email package.

R. David Murray added the comment: Final doc edits done. I will commit this next week if there are no objections, in order to get it in to alpha 4. -- Added file: http://bugs.python.org/file32055/master_content_manager.patch ___ Python tracker

[issue19082] Lib/xmlrpc/client.py demo code points to the dead server

Vajrasky Kok added the comment: Okay, I updated the patch. Now, it sends the datetime object instead of formatted datetime string. Also, I used static method inside instance to let the client uses dotted attribute feature instead of self attribute trick. -- Added file: http://bugs.pyth

[issue16355] inspect.getcomments() does not work in the interactive shell

Vajrasky Kok added the comment: Added the doc fix and modified the test. -- Added file: http://bugs.python.org/file32057/issue16355_v3.diff ___ Python tracker ___ ___

[issue19224] Make hash(None) consistent among processes

Tim Peters added the comment: -0. Since hash(None) is currently based on None's memory address, I appreciate that it's not reliable (e.g., use different releases of the same compiler to build Python, and hash(None) may be different between them). The docs guarantee little about hash() results

[issue19227] test_multiprocessing_xxx hangs under Gentoo buildbots

Charles-François Natali added the comment: > R. David Murray added the comment: OSError: [Errno 23] Too many open files in system: '/home/rdmurray/p34/Lib/tarfile.py' Well, the buildbot is hitting ENFILE. Try to run "lsof" as root, to see which process (more likely processes) have so many open

[issue19227] test_multiprocessing_xxx hangs under Gentoo buildbots

Charles-François Natali added the comment: > Here is a more useful traceback: If the failures aren't linked to ENFILE, then you could use strace to find the process on which the test is doing a waitpid(), and then perform an strace and gdb on that process to see where it's stuck. And send it a f

<    1   2