[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

[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

[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

[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()

[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

[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 <

[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

[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

[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

[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

[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

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

[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

[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

[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

[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 ___ _

[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 ___ __

[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 ___ __

[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: See also issue #8428. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue8428] buildbot: test_multiprocessing timeout

STINNER Victor added the comment: See also issue #8429. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue8355] diff.py produce unified format by default

Benjamin Peterson added the comment: -1 Even if diff.py is not exaclty a diff replacement, it still makes sense to emulate what's in people's minds. I really don't find having to type 3 more characters a very convincing argument. -- nosy: +benjamin.peterson status: open -> closed ___

[issue7332] python script segment fault at PyMarshal_ReadLastObjectFromFile in import_submodule

Charles-Francois Natali added the comment: It's definitely a stack overflow. Most of the backtraces show an important number of frames. The last frame is this: #0 PyMarshal_ReadLastObjectFromFile (fp=0x13e8200) at ../Python/marshal.c:1026 filesize = and a disassembly show us that

[issue762963] timemodule.c: Python loses current timezone

Paul Boddie added the comment: Well, this still doesn't work for me. I'm running Kubuntu 8.04 (libc6 package version 2.7-10ubuntu5) and reside in the CEST time zone, yet attempting to display the time zone always seems to give "+". Here are the failing tests, too: ===

[issue8429] buildbot: test_subprocess timeout

New submission from STINNER Victor : test_subprocess hungs for 30 min or more. The bug occurs on buildbots: - ARMv7Thumb Ubuntu 3.1 (r80093) - ARMv4 Debian 3.x (r80102) - ARMv7Thumb Ubuntu 3.x (r80020) - alpha Debian 3.x (r80020) - x86 FreeBSD 7.2 3.x (r80102) - sparc Debian trunk (r80085)

[issue8428] buildbot: test_multiprocessing timeout

STINNER Victor added the comment: The error occurs on buildbots: - i386 Ubuntu 3.x (r80115) - x86 FreeBSD 7.2 3.x (r80116, r80075) - x86 XP-4 3.x (r80115, r80106) -- ___ Python tracker __

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

Benjamin Peterson added the comment: And here's a patch for the correct Python version... -- Added file: http://bugs.python.org/file16956/no_dict_non_string_kwarg.patch ___ Python tracker __

[issue8425] a -= b should be fast if a is a small set and b is a large set

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue8421] tiger buildbot: unable to resolv hostname address

David Bolen added the comment: Looks like some initial configuration glitches - the buildbot needed a little convincing to go to the DNS server for gethostbyname(). Should be working now. -- ___ Python tracker __

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

Benjamin Peterson added the comment: Here's a patch. It adds a new function, PyArg_ValidateKeywordArguments. -- keywords: +patch Added file: http://bugs.python.org/file16955/no_dict_non_string_keyword_args.patch ___ Python tracker

[issue8322] test_ssl failures with OpenSSL 1.0.0

Changes by Antoine Pitrou : -- stage: needs patch -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue8322] test_ssl failures with OpenSSL 1.0.0

Antoine Pitrou added the comment: New patch updating docs. -- Added file: http://bugs.python.org/file16954/ciphers2.patch ___ Python tracker ___ _

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

Benjamin Peterson added the comment: They are already checked for pure python functions. -- nosy: +benjamin.peterson ___ Python tracker ___ __

[issue7811] [decimal] ValueError -> TypeError in from_tuple

Raymond Hettinger added the comment: I could see a TypeError for the outer tuple a tuple wasn't passed-in. If the contents aren't what we expect, I believe that calling it a ValueError is the Python way. -- ___ Python tracker

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

Raymond Hettinger added the comment: Does this mean that every time someone uses **kwds, that the entire dictionary will need to be scanned for invalid keys? So every API that accepts and passes through **kwds will be slowed on every time it is called. Is there any offsetting benefit?

[issue8428] buildbot: test_multiprocessing timeout

New submission from STINNER Victor : Example: http://www.python.org/dev/buildbot/3.x/builders/x86 FreeBSD 7.2 3.x/builds/480/steps/test/logs/stdio --- test_multiprocessing test test_multiprocessing failed -- Traceback (most recent call last): File "/usr/home/db3l/buildarea/3.x.bolen-

[issue8427] toplevel jumps to another location on the screen

New submission from Andrei Paraschivescu : The effect is the window just jumps to another location, matching left corners with another window in the same Python application. Its size doesn't change. The effect is somewhat erratic, the best I've been able to create is a situation where it happ

[issue8322] test_ssl failures with OpenSSL 1.0.0

Changes by Antoine Pitrou : Added file: http://bugs.python.org/file16953/ciphers.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8322] test_ssl failures with OpenSSL 1.0.0

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file16952/ciphers.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue8322] test_ssl failures with OpenSSL 1.0.0

Antoine Pitrou added the comment: A set_ciphers() method turns out to be highly impractical, since the underlying SSL objects are created lazily when we actually connect the socket. Therefore, I have instead opted for a new "ciphers" argument to the SSL constructor(s). Patch attached. ---

[issue7811] [decimal] ValueError -> TypeError in from_tuple

Mark Dickinson added the comment: >From both practical and purity points of view I think I prefer TypeError for >the cases Stefan gives: if you're passing a float for the sign, then you've >somehow ended up with the wrong type for that sign, and that's a TypeError >rather than a ValueError.

[issue8299] Improve GIL in 2.7

Kristján Valur Jónsson added the comment: What your fair.py is doing is demonstrating the superior behaviour of a time-based GIL interrupt to a bytecode based one. I have no quibbles with that and I agree that it is superior. But I also think that your example is a very artificial one. On

[issue8108] test_ftplib fails with OpenSSL 0.9.8m

Antoine Pitrou added the comment: After thinking a bit about it, we're in quasi-feature freeze now for 2.x and it doesn't sound reasonable to add options to unwrap(); we would need to write tests to exercise these options and their behaviour. Also, they aren't strictly needed to fix the issue

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

Changes by R. David Murray : -- title: move test_support into the unittest package -> move generally useful test_support functions into the unittest package ___ Python tracker __

[issue8273] move test_support into the unittest package

Raymond Hettinger added the comment: -1 on moving the module into the mainstream without significant reworking and rethinking. This module is a junk collection (I know because I've contributed some it). The unittest module is important. It needs a super clean, well thought out API. The te

[issue8273] move test_support into the unittest package

R. David Murray added the comment: I'm writing unittests for a program I'm writing, and would really love to be able to use captured_stdout/stderr. Of course, I have to support Python 2.5, and can't really justify installing unittest2, so I'll have to roll my own anyway, but I'm definitely +

[issue8425] a -= b should be fast if a is a small set and b is a large set

Changes by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger versions: +Python 3.3 -Python 3.1 ___ Python tracker ___ _

[issue8424] tiger buildbot: test_itimer_virtual failures

Changes by Martin v. Löwis : -- keywords: +buildbot ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8423] tiger buildbot: test_pep277 failures

Changes by Martin v. Löwis : -- keywords: +buildbot ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue7811] [decimal] ValueError -> TypeError in from_tuple

Raymond Hettinger added the comment: A ValueError seems more appropriate to me. -- nosy: +rhettinger ___ Python tracker ___ ___ Python

[issue8422] tiger buildbot: test_abspath_issue3426 failure (test_genericpath.py)

Changes by Martin v. Löwis : -- keywords: +buildbot ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue8421] tiger buildbot: unable to resolv hostname address

Martin v. Löwis added the comment: David, can you take a look? -- nosy: +db3l, loewis ___ Python tracker ___ ___ Python-bugs-list mail

[issue8426] multiprocessing.Queue fails to get() very large objects

New submission from Ian Davis : I'm trying to parallelize some scientific computing jobs using multiprocessing.Pool. I've also tried rolling my own Pool equivalent using Queues. In trying to return very large result objects from Pool.map()/imap() or via Queue.put(), I've noticed that multipr

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

Alex added the comment: Guido seems to be favoring disallowing it, not ignoring it[0]. http://mail.python.org/pipermail/python-dev/2010-April/099435.html -- nosy: +alex ___ Python tracker _

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

Eric Smith added the comment: I agree with Mark. Guido's point was that if it's implementation defined, you'll have portability problems: http://mail.python.org/pipermail/python-dev/2010-April/099435.html -- ___ Python tracker

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

Mark Dickinson added the comment: > I agree with Guido that we just call this an undefined, implementation > specific behavior. Actually I think that was exactly what Guido was *disagreeing* with. :) -- ___ Python tracker

[issue8401] Strange behavior of bytearray slice assignment

Martin v. Löwis added the comment: -1 on assigning strings to slices of bytearrays. As Ezio mentions, this operation conceptually requires an encoding, and no encoding is readily available in the slice assignment. -1 on special-casing empty strings. -- __

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

Raymond Hettinger added the comment: I don't think this is worth the performance hit or worth the deprecate/remove exercise. I agree with Guido that we just call this an undefined, implementation specific behavior. This behavior has existed for a very long time with no ill-effects. Marking

[issue8425] a -= b should be fast if a is a small set and b is a large set

New submission from Eugene Kapun : >>> small_set = set(range(2000)) >>> large_set = set(range(2000)) >>> large_set -= small_set # Fast >>> small_set -= large_set # Slow, should be fast >>> small_set = small_set - large_set # Fast -- components: Interpreter Core messages: 103343 nosy:

[issue7811] [decimal] ValueError -> TypeError in from_tuple

Mark Dickinson added the comment: It's a bit ambiguous: the object being supplied to the Decimal constructor does have the right type (tuple), but the wrong contents (i.e., value). So you could argue either way on this, I guess. -- assignee: -> mark.dickinson _

[issue8424] tiger buildbot: test_itimer_virtual failures

New submission from STINNER Victor : test_itimer_virtual (test.test_signal.ItimerTest) ... FAIL == FAIL: test_itimer_prof (test.test_signal.ItimerTest) -- Trace

[issue8423] tiger buildbot: test_pep277 failures

New submission from STINNER Victor : http://www.python.org/dev/buildbot/3.x/builders/x86 Tiger 3.x/builds/6/steps/test/logs/stdio test test_pep277 failed -- multiple errors occurred; run in verbose mode for details Re-running test test_pep277 in verbose mode test_directory (test.test_pep277.Un

[issue4970] test_os causes delayed failure on x86 gentoo buildbot: Unknown signal 32

Mark Dickinson added the comment: Fix merged to release31-maint in r80119. Thanks, Victor. -- components: +Tests resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> crash ___ Python tracker

[issue8422] tiger buildbot: test_abspath_issue3426 failure (test_genericpath.py)

Changes by STINNER Victor : -- components: +Library (Lib) versions: +Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue8422] tiger buildbot: test_abspath_issue3426 failure (test_genericpath.py)

New submission from STINNER Victor : http://www.python.org/dev/buildbot/3.x/builders/x86 Tiger 3.x/builds/6/steps/test/logs/stdio test test_ntpath failed -- Traceback (most recent call last): File "/Users/db3l/buildarea/3.x.bolen-tiger/build/Lib/test/test_genericpath.py", line 288, in test_

[issue8421] tiger buildbot: unable to resolv hostname address

New submission from STINNER Victor : http://www.python.org/dev/buildbot/3.x/builders/x86 Tiger 3.x/builds/6/steps/test/logs/stdio: == ERROR: testSockName (test.test_socket.GeneralModuleTests)

[issue1766304] improve xrange.__contains__

Raymond Hettinger added the comment: As an implementation detail, it isn't too late to put this into 2.x if it is something we care about. -- priority: normal -> low ___ Python tracker _

[issue8413] String interpolation doesn't work with sys.version_info

Changes by Raymond Hettinger : -- priority: normal -> high ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue8420] set_lookkey is unsafe

Changes by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list U

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

Changes by Eric Smith : -- nosy: +eric.smith ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: > Commited: r80112 (py3k) Looks good: r80118 (3.1). -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue7605] test_cmd_line fails with non-ascii path

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue7605] test_cmd_line fails with non-ascii path

STINNER Victor added the comment: Fixed: r80116 (py3k), r80117 (3.1). -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue8420] set_lookkey is unsafe

New submission from Eugene Kapun : I've noticed that set_lookkey (in Objects/setobject.c) does some unsafe things: Objects/setobject.c: > if (entry->hash == hash) { > startkey = entry->key; > Py_INCREF(startkey); > cmp = PyObject_RichCompareBool(startkey, key, Py_EQ); > Py

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

Mark Dickinson added the comment: Update: IronPython also produces a TypeError here (thanks Michael Foord and Dino Viehland). -- ___ Python tracker ___

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

Mark Dickinson added the comment: The issue applies to dict.update as well: >>> d = {1:2} >>> d.update({3:4}, **{5:6}) >>> d {1: 2, 3: 4, 5: 6} -- ___ Python tracker ___ ___

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

Changes by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

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

New submission from Mark Dickinson : In all versions of CPython right now, the following works. >>> dict({1:2}, **{3:4}) {1: 2, 3: 4} Other Python implementations raise TypeError for this; CPython should probably do the same, beginning with deprecating this behaviour in Python 3.2 and removi

[issue7605] test_cmd_line fails with non-ascii path

STINNER Victor added the comment: The problem is that the print is failing because Python uses ASCII encoding for stdout. Attached patch encodes sys.path to ASCII using backslashreplace to avoid the encoding issue. -- keywords: +patch nosy: +haypo Added file: http://bugs.python.org/fi

[issue8418] Crash 0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER on program exit

R. David Murray added the comment: The meta-tracker (the tracker to report problems with the tracker) is a separate tracker and you have to create a new login there. I agree that this is awkward, but nobody has stepped up to fix it yet. 'your issues' is issues assigned to you, and 'normal' u

[issue8418] Crash 0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER on program exit

Alf P. Steinbach added the comment: It now seems almost certain that it's /necessary/ to not have run any Python programs for a while (say, 10 minutes?) in order for the bug to manifest when using Ctrl C in the enclosed program. Also, I forgot to mention, the SEH exception occurs *while the p

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

Changes by Nick Coghlan : -- assignee: -> ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

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

Jean-Paul Calderone added the comment: > The one big difference I can see is that set_wakeup_fd() doesn't transmit the > signal number, but this could be fixed if desired (instead of sending '\0', > send a byte containing the signal number). There's a lot more information than the signal numb

[issue8418] Crash 0xc0000417 STATUS_INVALID_CRUNTIME_PARAMETER on program exit

New submission from Alf P. Steinbach : Python 3.1.1 in Windows XP Prof, appears to be a Windows-only problem Effect: on program exit the interpreter crashes with exception 0xc417 STATUS_INVALID_CRUNTIME_PARAMETER at address 0x78588389, which appears to be in [msvcr90.dll]. To reproduce:

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

R. David Murray added the comment: @Éric: even if you prepare the patches, I find I'm not interested in doing the checkins. If someone else wants to take this on that's fine with me, but I'm not going to do it. -- assignee: georg.brandl -> ___ Py

[issue7606] test_xmlrpc fails with non-ascii path

STINNER Victor added the comment: Commited: r80112 (py3k). Waiting for the buildbots before te backport to 3.1. -- ___ Python tracker ___

[issue7606] test_xmlrpc fails with non-ascii path

Antoine Pitrou added the comment: > What do you think about my solution (convert the traceback to ASCII to > avoid the encoding issue)? It's fine for me. Perhaps you should add a comment to explain why this is necessary. -- ___ Python tracker

[issue762963] timemodule.c: Python loses current timezone

R. David Murray added the comment: Review the code, test the patch, confirm that it fixes the problem and doesn't break anything else, and report your results here. That doesn't guarantee that it will get applied, but it definitely helps. -- nosy: +r.david.murray ___

[issue7946] Convoy effect with I/O bound threads and New GIL

Nir Aides added the comment: I uploaded an update to bfs.patch which improves behavior in particular on non-Linux multi-core (4+) machines. Hi Charles-Francois, Thanks for taking the time to review this patch! > - nothing guarantees that you'll get a msec resolution Right, the code should b

[issue7946] Convoy effect with I/O bound threads and New GIL

Changes by Nir Aides : Removed file: http://bugs.python.org/file16830/bfs.patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue8408] need console/pager module

R. David Murray added the comment: Benjamin was using the term 'bug' as a synonym for 'issue in the tracker'. The point is that a feature like this (a whole new module) is not an appropriate tracker item. In most cases the procedure for getting a new module included in the stdlib is distinc

[issue8412] os.system() doesn't support surrogates nor bytes

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Un

[issue8412] os.system() doesn't support surrogates nor bytes

STINNER Victor added the comment: > Commited to py3k as r80105 The buildbots look happy: backported to 3.1 as r80110. -- ___ Python tracker ___ _

[issue8405] Improve test_os._kill (failing on slow machines)

STINNER Victor added the comment: With the patch, the test have 1.0 second to succeed. I would prefer 5.0 or 10.0 seconds: it should not waste the 10 seconds because it should succeed if a new milliseconds. But if the machine is "slow" (which is the topic of the issue), you can give some more

[issue4970] test_os causes delayed failure on x86 gentoo buildbot: Unknown signal 32

STINNER Victor added the comment: Commited as r80108 to py3k: "Add CS_GNU_LIBC_VERSION and CS_GNU_LIBPTHREAD_VERSION constants for constr(), and disable test_execvpe_with_bad_program() of test_os if the libc uses linuxthreads to avoid the "unknown signal 32" bug (see issue #4970)." Wait for

[issue8314] test_ctypes fails in test_ulonglong on sparc buildbots

STINNER Victor added the comment: > Committed as r79892. Commited to py3k (r80106), but blocked in 3.1 (r80107) because Python 3.1 uses libffi 3.0.5. -- nosy: +haypo status: pending -> open ___ Python tracker ___

[issue8413] String interpolation doesn't work with sys.version_info

Changes by R. David Murray : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue8412] os.system() doesn't support surrogates nor bytes

STINNER Victor added the comment: Commited to py3k as r80105. Let see if buildbots are happy or not :-) -- ___ Python tracker ___ ___

[issue8410] Fix emulated lock to be 'fair'

Kristján Valur Jónsson added the comment: Martin, it isn't the condition variable which is unfair, but how the constructed locking apparatus is unfair that is the problem. This lock is written by a Tim, whom I assume to be Tim Peters. I quote his comment: "In general, if the bit can be acq

[issue2987] RFC2732 support for urlparse (IPv6 addresses)

Senthil Kumaran added the comment: Reverted the check-in made to 3.1 maint (in r80104). Features should not go in there. -- ___ Python tracker ___ __

  1   2   >