[issue8428] buildbot: test_multiprocessing timeout

STINNER Victor added the comment: All builds ends with "test_multiprocessing" and then the buildbot kills the proces. Only "x86 FreeBSD 7.2 3.x" last build (480, not the others) show us that test_pool_worker_lifetime (test.test_multiprocessing.WithProcessesTestPoolWorkerLifetime) hung. -

[issue8429] buildbot: test_subprocess timeout

STINNER Victor added the comment: All builds ends with "test_subprocess" and then the process is killed. There is no usefull information :-/ -- ___ Python tracker ___ __

[issue8419] dict constructor allows invalid identifiers in **kwargs

Benjamin Peterson added the comment: Now with the suggested dictionary speed hack. -- Added file: http://bugs.python.org/file16957/with_speed_hack.patch ___ Python tracker ___ __

[issue8417] bytes and bytearray constructors raise TypeError for very large ints

Benjamin Peterson added the comment: Fixed in r80126. Thanks for the report! -- nosy: +benjamin.peterson resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue8355] diff.py produce unified format by default

Raymond Hettinger added the comment: I concur with Benjamin. -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing

[issue8421] tiger buildbot: unable to resolv hostname address

R. David Murray added the comment: Thanks, David. test_socket passed on the latest trunk run on the tiger buildbot. -- nosy: +r.david.murray resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tr

[issue8393] subprocess: support undecodable current working directory on POSIX OS

STINNER Victor added the comment: Commited in py3k (r80135), blocked in 3.1 (r80136). Python 3.1 has no _posixsubprocess module, it uses os.chdir() which accepts bytes, bytearray and str with surrogates. -- resolution: -> fixed status: open -> closed

[issue8362] Add Misc/maintainers.rst to 2.x branch

STINNER Victor added the comment: I read the maintainers list. I don't like empty lines. If a module has no maintainer, it should not be listed in this file. Since Python3 module names are different, if we copy the list to Python2, maintaining this list between Python2 and Python3 will be mor

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: If anyone would like to work on non-ASCII HTTP header, please open a new issue with a pointer to this one. -- ___ Python tracker ___ __

[issue8362] Add Misc/maintainers.rst to 2.x branch

R. David Murray added the comment: Any module without a listed maintainer is maintained by the community as a whole (as it says in the introduction). The fact that a module does not have a listed maintainer does not mean it is dead, and I don't think anyone(except you? :) thinks that. All m

[issue8299] Improve GIL in 2.7

David Beazley added the comment: I'm not trying to be a pain here, but do you have any explanation as to why, with fair scheduling, the observed execution time of multiple CPU-bound threads is substantially worse than with unfair scheduling? >From your own benchmarks, consider this result (Fa

[issue8299] Improve GIL in 2.7

David Beazley added the comment: One other comment. Running the modified fair.py file on my Linux system using Python compiled with semaphores shows they they are *definitely* not fair. Here's the relevant part of your test: Treaded, balanced execution, with quickstop: fast C: 1.580815 (0 l

[issue8418] Crash 0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER on program exit

Alf P. Steinbach added the comment: Thanks for explaining that. However, the first bug I ever reported was #7681, "Use floor division in appropiate places in the wave module.", fixed in 3.1.2. And the tracker search does not find this bug by id. Nor does it find it by specifying "wave" as te

[issue8273] move generally useful test_support functions into the unittest package

Ezio Melotti added the comment: Not the module as it is, but just some of the APIs that it provides, possibly after a cleanup to remove things specific to our test suite and to make them more general and forward-compatible. -- ___ Python tracker <

[issue8273] move generally useful test_support functions into the unittest package

Raymond Hettinger added the comment: If anything gets moved, it needs to be part of a very well thought-out plan with the same high threshold for approval that it would have had if it weren't in test_support. The unittest module already brims with complexity and would suffer quite a bit if a

[issue3864] 26.rc1: test_signal issue on FreeBSD 6.3

R. David Murray added the comment: The FreeBSD bot in question is now running 6.4, and test_signal is still failing. I have access to a 6.3 box, which shows exactly the same failures as I see in the buildbot log. On that box, doing t = threading.Thread(target=lambda: None) t.start()

[issue8263] regrtest stops prematurately on FreeBSD buildbot, with "success" result.

R. David Murray added the comment: I can reliably reproduce the SIGINT problem on a FreeBSD 6.3 box, if (and so far only if) some test that uses threading is run first (see also issue 3864). So I suspect this is a freebsd6 specific problem and just needs a skip added. -- nosy: +r.dav

[issue8424] tiger/FreeBSD7.2 buildbots: test_itimer_virtual failures

R. David Murray added the comment: The FreeBSD 7.2 buildbot also shows this failure. See also issue 3864; although this failure appears to be slightly different, it might be due to a remnant of the same platform bug. I'm making everyone from that bug nosy on this one. -- components

[issue8418] Crash 0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER on program exit

R. David Murray added the comment: That's because 7681 is closed. (That said, I consider it a bug in the tracker that it defaults to searching only open issues...and I think I filed an issue in the metatracker for that, too. Maybe I'll get around to fixing it if I can get agreement that fix

<    1   2