[issue13545] Pydoc3.2: TypeError: unorderable types
Peter Frauenglass python@everblue.info added the comment: I should also mention that pydoc2.7 -p 1234 works without issue. It seems to be a regression. Also adding lemburg to the Nosy list as the comments on platform.py suggest. -- nosy: +lemburg ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13545 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13542] Memory leak in multiprocessing.pool
Changes by Ezio Melotti ezio.melo...@gmail.com: -- nosy: +jnoller stage: - needs patch versions: -Python 2.6, Python 3.1, Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
New submission from Ji Han hanji1...@gmail.com: The following code snippet will crash IDLE: import sys sys.setrecursionlimit((131)-1) The crash happens immediately and is consistently reproducible (environment: Windows 7 SP1 64-bit, Python 2.7.2 for Windows X86_64). -- components: None messages: 148953 nosy: hanji priority: normal severity: normal status: open title: sys.setrecursionlimit() crashes IDLE versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8641] IDLE 3 doesn't highlights b, but u
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 3822c8087d70 by Ned Deily in branch '3.2': Issue #8641: Update IDLE 3 syntax coloring to recognize b.. and not u... http://hg.python.org/cpython/rev/3822c8087d70 New changeset e49220f4c31f by Ned Deily in branch 'default': Issue #8641: Update IDLE 3 syntax coloring to recognize b.. and not u... http://hg.python.org/cpython/rev/e49220f4c31f -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8641 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8641] IDLE 3 doesn't highlights b, but u
Ned Deily n...@acm.org added the comment: Thanks for the patch, Tal, and thanks for testing it, Roger. Applied to 3.2 for release in 3.2.3 and to default for 3.3.0. -- assignee: - ned.deily nosy: +ned.deily resolution: works for me - fixed stage: - committed/rejected status: open - closed versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8641 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Ned Deily n...@acm.org added the comment: Trying to set the recursion limit to a large number defeats its purpose. As documented in the Standard Library Reference: The highest possible limit is platform-dependent. A user may need to set the limit higher when she has a program that requires deep recursion and a platform that supports a higher limit. This should be done with care, because a too-high limit can lead to a crash. http://docs.python.org/library/sys.html#sys.setrecursionlimit -- nosy: +ned.deily resolution: - wont fix stage: - committed/rejected status: open - closed type: - crash ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: On the other hand, there is no reason for the recursion limit to be actually reached, just by setting it! Is there a hidden infinite recursion somewhere? -- nosy: +amaury.forgeotdarc ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: hanji, could you start IDLE from a command prompt and try again: c:\python27\python.exe -m idlelib.idle Do you see additional error messages? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Zbyszek Szmek zbys...@in.waw.pl added the comment:
f((yield))
This requirement seems unnecessary. And surprising, because
f(generator-expression) or f('a' if 'a' else 'b') doesn't require parenthes.
There's no room for confusion if parentheses were omitted in the
single-argument case. (Following the rule given in documentation for generator
expressions: The parentheses can be omitted on calls with only one argument.).
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11682
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Ned Deily n...@acm.org added the comment: But after setting it, IDLE is going to be executing code. In the 64-bit Windows Python 2.7.2 that I have available, there were exceptions reported in the command line interpreter (not IDLE) after changing the recursion limit and then executing some code. Perhaps there is another of the known overflow error issues here. OTOH, similar reports have also been closed as won't fix, most recently Issue12468. This doesn't seem worth the effort to investigate further. Feel free to reopen if you disagree. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Ji Han hanji1...@gmail.com added the comment: @amaury.forgeotdarc It says 'python.exe has stopped working'. Details: Problem Event Name: APPCRASH Application Name: python.exe Application Version: 0.0.0.0 Application Timestamp:4df4b010 Fault Module Name:MSVCR90.dll Fault Module Version: 9.0.30729.6161 Fault Module Timestamp: 4dace4e7 Exception Code: c0fd Exception Offset: 0001edcf ... ... ... P.S. I'm well aware recursions won't go that deep. But crashing IDLE (instead of Raising an Error) by simply setting an option is still annoying. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13545] Pydoc3.2: TypeError: unorderable types
Antoine Pitrou pit...@free.fr added the comment: This seems to be an issue with the platform module's detection of the glibc. Can you tell us more about your system? (OS, distribution...) -- nosy: +pitrou, r.david.murray versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13545 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Changes by Nick Coghlan ncogh...@gmail.com: Removed file: http://bugs.python.org/file23216/0001.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Changes by Nick Coghlan ncogh...@gmail.com: Removed file: http://bugs.python.org/file23570/issue11682_pep380_branch_2031.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Changes by Nick Coghlan ncogh...@gmail.com: Removed file: http://bugs.python.org/file23759/0001-2.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Changes by Nick Coghlan ncogh...@gmail.com: Removed file: http://bugs.python.org/file23639/test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Changes by Nick Coghlan ncogh...@gmail.com: -- hgrepos: -11 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Nick Coghlan ncogh...@gmail.com added the comment: OK, I removed all the old files and repo links (they're still available in the history below if needed). (well, the link to Renaud's hg patch queue is gone, but that's also present in one of the early comments). (Ron: your comment makes me think you were looking at an old version of the PEP 380 updates. The most up to date published version is the tip of my BitBucket branch) Also, don't spend a lot of time messing with functional aspects of the patch folks, especially the Grammar. 'yield from' is going to be a variant of the existing yield expressions to avoid parser ambiguity, and it's going to inherit all of the associated restrictions, including the requirement for parentheses when it's the sole argument to a function. While that restriction isn't *necessary*, it's also irrelevant to this PEP (hence why I reverted Greg's changes that allowed it for 'yield from', but not for other yield expressions). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Nick Coghlan ncogh...@gmail.com added the comment: As far as *why* yield expressions aren't special cased the way generator expressions are - just an oversight when yield expressions were added, no real grand master plan. It's not a big deal in practice, so nobody has ever cared enough to argue for fixing it. Conditional expressions simply don't include mandatory parentheses as part of the syntax in the first place. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11610] Improved support for abstract base classes with descriptors
Darren Dale dsdal...@gmail.com added the comment: New patch addressing comments in review. -- Added file: http://bugs.python.org/file23864/abc_descriptor.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11610 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: Tested on Linux: Python 2.7.2+ (2.7:16c4137a413c+, Dec 4 2011, 22:56:38) [GCC 4.4.3] on linux2 import sys sys.setrecursionlimit((131)-1) import xx Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.ImportError' ignored Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in type 'exceptions.ImportError' ignored Traceback (most recent call last): This comes from PyErr_GivenExceptionMatches() which tries to Temporarily bump the recursion limit, and calls Py_SetRecursionLimit(reclimit + 5); without any consideration for 32bit int overflow... and PyErr_WriteUnraisable() is called to display the error. IDLE crashes (with a real stack overflow) because sys.stderr is a special RPCProxy object whose methods are found through a __getattr__. But __getattr__ is called when __getattribute__ raises AttributeError, right? To implement this, PyErr_GivenExceptionMatches() is called again, fails again, call PyErr_WriteUnraisable()... recursively. The fix should be easy: do not bump the recursion limit when it's already too high. -- resolution: wont fix - stage: committed/rejected - needs patch status: closed - open ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13545] Pydoc3.2: TypeError: unorderable types
maniram maniram maniandra...@gmail.com added the comment: On my system it works. :-) -- nosy: +maniram.maniram ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13545 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13545] Pydoc3.2: TypeError: unorderable types
STINNER Victor victor.stin...@haypocalc.com added the comment: Can you try to patch platform.py with the following patch? diff --git a/Lib/platform.py b/Lib/platform.py --- a/Lib/platform.py +++ b/Lib/platform.py @@ -186,7 +186,7 @@ def libc_ver(executable=sys.executable,l elif so: if lib != 'glibc': lib = 'libc' -if soversion version: +if soversion and soversion version: version = soversion if threads and version[-len(threads):] != threads: version = version + threads -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13545 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13547] Clean Lib/_sysconfigdata.py and Modules/_testembed
New submission from Stefan Krah stefan-use...@bytereef.org: I think that `make distclean` should remove Lib/_sysconfigdata.py and Modules/_testembed. On second thought, `make clean` should probably also remove those. -- components: Build messages: 148969 nosy: skrah priority: normal severity: normal stage: needs patch status: open title: Clean Lib/_sysconfigdata.py and Modules/_testembed type: behavior versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13547] Clean Lib/_sysconfigdata.py and Modules/_testembed
Antoine Pitrou pit...@free.fr added the comment: Yes, make clean should remove them as well. -- nosy: +pitrou versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13547 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13500] Hitting EOF gets cmd.py into a infinite EOF on return loop
Éric Araujo mer...@netwok.org added the comment: I believe the commit would have needed a regression test. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13500] Hitting EOF gets cmd.py into a infinite EOF on return loop
Garrett Cooper yaneg...@gmail.com added the comment: I'll verify the fix in another day or two. FWIW unless python is willing to import pexpect, or provide an equivalent, I'm not sure how items like this which require interactive input can be run via the python project testing framework. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13500] Hitting EOF gets cmd.py into a infinite EOF on return loop
Éric Araujo mer...@netwok.org added the comment: I'm not sure how items like this which require interactive input can be run via the python project testing framework. Replace sys.stdin with a custom object (a stub) and you can control input (see the Inputs class used in Lib/packaging/tests/test_create.py or Lib/packaging/tests/test_command_register.py). The readline module would not be used however, so that can’t be tested. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13548] Invalid 'line' tracer event on pass within else clause
New submission from Stephan R.A. Deibel sdei...@wingware.com: The tracer set with sys.settrace() is called incorrectly with a 'line' event on a 'pass' that is at the end of an 'else' clause on the final line of a function even if the else block is not executed by the interpreter. Whew, talk about an end case! The attached file illustrates this. -- components: Interpreter Core files: badlineevent.py messages: 148974 nosy: sdeibel priority: normal severity: normal status: open title: Invalid 'line' tracer event on pass within else clause type: behavior versions: Python 2.6, Python 2.7, Python 3.1, Python 3.2 Added file: http://bugs.python.org/file23865/badlineevent.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13548] Invalid 'line' tracer event on pass within else clause
Changes by Ned Batchelder n...@nedbatchelder.com: -- nosy: +nedbat ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13548] Invalid 'line' tracer event on pass within else clause
Stephan R.A. Deibel sdei...@wingware.com added the comment: Sorry, the print statement in the file needs a tweak to work with Python 3.2, but the bug does occur there also. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13500] Hitting EOF gets cmd.py into a infinite EOF on return loop
Garrett Cooper yaneg...@gmail.com added the comment: Ok. I'll see if I can provide a unittest for this by the 12th. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13500 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Ron Adam ron3...@gmail.com added the comment: Thanks for the updated links Nick. There is a comment in the docs that recommends putting parentheses around any yield expression that returns a value. So it is in agreement with that in the function argument case. The grammar I used does keep it as a variant. yield_expr 'yield' [testlist | yield_from] yield_from 'from' test The purpose of doing that is so I can do ... yield_expr 'yield' [testlist | yield_from | yield_raise] yield_from 'from' test yield_raise 'raise' [test ['from' test]] The yield_raise part is only an interesting exercise to help me understand cpythons internals better. I'm getting there and hope to be able to contribute to more bug fixes, and patches. :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11682 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13394] Patch to increase aifc lib test coverage with couple of minor fixes
Ezio Melotti ezio.melo...@gmail.com added the comment: I think the patch includes too many changes. It would be better if you can split it in two separate patches: one with the increased coverage, the other with the bugs you found and their tests. I can easily commit the first (assuming it doesn't break the test suite), but the second requires someone familiar with the aifc module for a review. If you have found (and fixed) several unrelated bugs in aifc, it might be better to split the second patch further, and possibly open different issues, stating what the bugs are and how you fixed them. -- nosy: +ezio.melotti ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13394 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13531] add test for defaultdict with non-callable first argument
Changes by Ezio Melotti ezio.melo...@gmail.com: -- assignee: - ezio.melotti stage: test needed - commit review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13531 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13534] test_cmath fails on ppc with glibc-2.14.90 due to buggy architecture-specific hypot
Dave Malcolm dmalc...@redhat.com added the comment: I agree. I filed this here in case anyone else ran into it, but given that this is really a glibc bug (now fixed), I'm closing this out as won't fix. -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13534 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13542] Memory leak in multiprocessing.pool
Charles-François Natali neolo...@free.fr added the comment: It's a duplicate of #12157. -- nosy: +neologix resolution: - duplicate stage: needs patch - committed/rejected status: open - closed superseder: - join method of multiprocessing Pool object hangs if iterable argument of pool.map is empty ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13542 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11051] system calls per import
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset a541bda2f5e2 by Charles-François Natali in branch 'default': Issue #11051: Reduce the number of syscalls per import. http://hg.python.org/cpython/rev/a541bda2f5e2 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11051 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11051] system calls per import
Martin v. Löwis mar...@v.loewis.de added the comment: I would have appreciated had you considered my review before pushing that change. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11051 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11051] system calls per import
Charles-François Natali neolo...@free.fr added the comment: I would have appreciated had you considered my review before pushing that change. Sorry, I didn't receive an email notification for your review, so I didn't know you had done one. I'll add a comment. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11051 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13502] Documentation for Event.wait return value is either wrong or incomplete
Charles-François Natali neolo...@free.fr added the comment: Here's a patch. -- keywords: +patch Added file: http://bugs.python.org/file23866/event_wait_cleared.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13502 ___diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst --- a/Doc/library/threading.rst +++ b/Doc/library/threading.rst @@ -804,8 +804,9 @@ floating point number specifying a timeout for the operation in seconds (or fractions thereof). - This method returns the internal flag on exit, so it will always return - ``True`` except if a timeout is given and the operation times out. + This method returns true if and only if the internal flag has been set to + true by another thread, so it will always return ``True`` except if a + timeout is given and the operation times out. .. versionchanged:: 3.1 Previously, the method always returned ``None``. diff --git a/Lib/test/lock_tests.py b/Lib/test/lock_tests.py --- a/Lib/test/lock_tests.py +++ b/Lib/test/lock_tests.py @@ -353,6 +353,22 @@ for r, dt in results2: self.assertTrue(r) +def test_set_and_clear(self): +# Issue #13502: check that wait() returns true even when the event is +# cleared before the waiting thread is woken up. +evt = self.eventtype() +results = [] +N = 5 +def f(): +results.append(evt.wait(1)) +b = Bunch(f, N) +b.wait_for_started() +time.sleep(0.5) +evt.set() +evt.clear() +b.wait_for_finished() +self.assertEqual(results, [True] * N) + class ConditionTests(BaseTestCase): diff --git a/Lib/threading.py b/Lib/threading.py --- a/Lib/threading.py +++ b/Lib/threading.py @@ -408,9 +408,10 @@ def wait(self, timeout=None): self._cond.acquire() try: -if not self._flag: -self._cond.wait(timeout) -return self._flag +signaled = self._flag +if not signaled: +signaled = self._cond.wait(timeout) +return signaled finally: self._cond.release() ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13453] Tests and network timeouts
Charles-François Natali neolo...@free.fr added the comment: URLError: urlopen error [Errno 4] Non-recoverable failure in name resolution For this one, we should probably add EAI_FAIL to support.transient_internet. -- keywords: +patch nosy: +neologix Added file: http://bugs.python.org/file23867/transient.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13453 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: Here is a patch, with test. -- keywords: +patch Added file: http://bugs.python.org/file23868/issue13546.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Changes by Amaury Forgeot d'Arc amaur...@gmail.com: -- assignee: - amaury.forgeotdarc stage: needs patch - patch review ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Ned Deily n...@acm.org added the comment: LGTM -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 57de1ad15c54 by Amaury Forgeot d'Arc in branch '2.7': Issue #13546: Fixed an overflow issue that could crash the intepreter when http://hg.python.org/cpython/rev/57de1ad15c54 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13546] sys.setrecursionlimit() crashes IDLE
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: This will be fixed in the next 2.7 release, thanks for the report! -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13546 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1602] windows console doesn't print or input Unicode
Matt Mackall m...@selenic.com added the comment: The underlying cause of Python's write exceptions with cp65001 is: The ANSI C write() function as implemented by the Windows console returns the number of _characters_ written rather than the number of _bytes_, which Python reasonably interprets as a short write error. It then consults errno, which gives the effectively random error message seen. This can be bypassed by using os.write(sys.stdout.fileno(), utf8str), which will a) succeed and b) return a count = len(utf8str). With os.write() and an appropriate font, the Windows console will correctly display a large number of characters. Possible workaround: clear errno before calling write, check for non-zero errno after. The vast majority of (non-Python) applications never check the return value of write, so don't encounter this problem. -- nosy: +Matt.Mackall ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue1602 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
STINNER Victor victor.stin...@haypocalc.com added the comment: I got the debug output of test_3_join_in_forked_from_thread() using some hacks (threading._VERBOSE=True and don't hide subprocess output): Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, verbose=0, bytes_warning=0, quiet=0) [ 1] test_threading test_3_join_in_forked_from_thread (test.test_threading.ThreadJoinOnShutdown) ... OS thread 13968376176: Condition(_thread.lock object at 0x7f0aa24b8e50, 0).notify(): no waiters MainThread: Thread(Thread-1, initial).start(): starting thread OS thread 139683646777088: Condition(_thread.lock object at 0x7f0aa24b8b80, 1).notify(): notifying 1 waiter Thread-1: Thread(Thread-1, started 139683646777088)._bootstrap(): thread started MainThread: Condition(_thread.lock object at 0x7f0aa24b8b80, 0).wait(): got it MainThread: Condition(_thread.lock object at 0x7f0aa24b8cc0, 0).notify(): no waiters MainThread: _MainThread(MainThread, stopped 13968376176): waiting for other threads MainThread: Thread(Thread-1, started 139683646777088).join(): waiting until thread stops end of main Thread-1: Thread(Thread-2, initial).start(): starting thread OS thread 139683638384384: Condition(_thread.lock object at 0x7f0aa24b8b30, 1).notify(): notifying 1 waiter Thread-2: Thread(Thread-2, started 139683638384384)._bootstrap(): thread started Thread-1: Condition(_thread.lock object at 0x7f0aa24b8b30, 0).wait(): got it Thread-2: _MainThread(MainThread, stopped 13968376176).join(): thread stopped Thread-1: Thread(Thread-2, started 139683638384384).join(): waiting until thread stops end of thread Thread-2: Thread(Thread-2, started 139683638384384)._bootstrap(): normal return Thread-2: Condition(_thread.lock object at 0x7f0aa24b8b80, 1).notify(): notifying 1 waiter Thread-1: Condition(_thread.lock object at 0x7f0aa24b8b80, 0).wait(): got it Thread-1: Thread(Thread-2, stopped 139683638384384).join(): thread stopped Thread-1: Thread(Thread-1, started 139683646777088)._bootstrap(): normal return Thread-1: _RLock owner='Thread-1' count=1.acquire(True): initial success Thread-1: Condition(_RLock owner='Thread-1' count=1, 0).notify(): no waiters Thread-1: _RLock owner=None count=0.release(): final release Thread-1: Thread(Thread-1, started 139683646777088)._bootstrap(): raised SystemExit Thread-1: Condition(_thread.lock object at 0x7f0aa24b8bd0, 1).notify(): notifying 1 waiter MainThread: Condition(_thread.lock object at 0x7f0aa24b8bd0, 0).wait(): got it MainThread: Thread(Thread-1, stopped 139683646777088).join(): thread stopped MainThread: _MainThread(MainThread, stopped 13968376176): exiting [47121 refs] ok -- Ran 1 test in 0.095s OK [ 2] test_threading test_3_join_in_forked_from_thread (test.test_threading.ThreadJoinOnShutdown) ... OS thread 140303874844416: Condition(_thread.lock object at 0x7f9b03ea4e50, 0).notify(): no waiters MainThread: Thread(Thread-1, initial).start(): starting thread OS thread 140303759861504: Condition(_thread.lock object at 0x7f9b03ea4b80, 1).notify(): notifying 1 waiter Thread-1: Thread(Thread-1, started 140303759861504)._bootstrap(): thread started MainThread: Condition(_thread.lock object at 0x7f9b03ea4b80, 0).wait(): got it MainThread: Condition(_thread.lock object at 0x7f9b03ea4cc0, 0).notify(): no waiters MainThread: _MainThread(MainThread, stopped 140303874844416): waiting for other threads MainThread: Thread(Thread-1, started 140303759861504).join(): waiting until thread stops end of main -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
STINNER Victor victor.stin...@haypocalc.com added the comment: Hum, it's better with the process identifiers. Oh, by the way: the output is not truncated, Python test hangs during the second run :-) Without the debug output, it needs more than 1,000 runs to reproduce the bug (hang). Testing with flags: sys.flags(debug=0, inspect=0, interactive=0, optimize=0, dont_write_bytecode=0, no_user_site=0, no_site=0, ignore_environment=0, verbose=0, bytes_warning=0, quiet=0) [ 1] test_threading test_3_join_in_forked_from_thread (test.test_threading.ThreadJoinOnShutdown) ... pid 25114: OS thread 140143566120704: Condition(_thread.lock object at 0x7f75b0c54e50, 0).notify(): no waiters pid 25114: MainThread: Thread(Thread-1, initial).start(): starting thread pid 25114: OS thread 140143451137792: Condition(_thread.lock object at 0x7f75b0c54b80, 1).notify(): notifying 1 waiter pid 25114: Thread-1: Thread(Thread-1, started 140143451137792)._bootstrap(): thread started pid 25114: MainThread: Condition(_thread.lock object at 0x7f75b0c54b80, 0).wait(): got it pid 25114: MainThread: Condition(_thread.lock object at 0x7f75b0c54cc0, 0).notify(): no waiters pid 25114: MainThread: _MainThread(MainThread, stopped 140143566120704): waiting for other threads pid 25114: MainThread: Thread(Thread-1, started 140143451137792).join(): waiting until thread stops end of main pid 25116: Thread-1: Thread(Thread-2, initial).start(): starting thread pid 25116: OS thread 140143373580032: Condition(_thread.lock object at 0x7f75b0c54b30, 1).notify(): notifying 1 waiter pid 25116: Thread-2: Thread(Thread-2, started 140143373580032)._bootstrap(): thread started pid 25116: Thread-2: _MainThread(MainThread, stopped 140143566120704).join(): thread stopped end of thread pid 25116: Thread-2: Thread(Thread-2, started 140143373580032)._bootstrap(): normal return pid 25116: Thread-1: Condition(_thread.lock object at 0x7f75b0c54b30, 0).wait(): got it pid 25116: Thread-2: Condition(_thread.lock object at 0x7f75b0c54b80, 0).notify(): no waiters pid 25116: Thread-1: Thread(Thread-2, stopped 140143373580032).join(): thread stopped pid 25116: Thread-1: Thread(Thread-1, started 140143451137792)._bootstrap(): normal return pid 25116: Thread-1: _RLock owner='Thread-1' count=1.acquire(True): initial success pid 25116: Thread-1: Condition(_RLock owner='Thread-1' count=1, 0).notify(): no waiters pid 25116: Thread-1: _RLock owner=None count=0.release(): final release pid 25114: Thread-1: Thread(Thread-1, started 140143451137792)._bootstrap(): raised SystemExit pid 25114: Thread-1: Condition(_thread.lock object at 0x7f75b0c54bd0, 1).notify(): notifying 1 waiter pid 25114: MainThread: Condition(_thread.lock object at 0x7f75b0c54bd0, 0).wait(): got it pid 25114: MainThread: Thread(Thread-1, stopped 140143451137792).join(): thread stopped pid 25114: MainThread: _MainThread(MainThread, stopped 140143566120704): exiting [47125 refs] ok -- Ran 1 test in 0.091s OK [ 2] test_threading test_3_join_in_forked_from_thread (test.test_threading.ThreadJoinOnShutdown) ... pid 25118: OS thread 139664631559936: Condition(_thread.lock object at 0x7f062e0bde50, 0).notify(): no waiters pid 25118: MainThread: Thread(Thread-1, initial).start(): starting thread pid 25118: OS thread 139664516577024: Condition(_thread.lock object at 0x7f062e0bdb80, 1).notify(): notifying 1 waiter pid 25118: Thread-1: Thread(Thread-1, started 139664516577024)._bootstrap(): thread started pid 25118: MainThread: Condition(_thread.lock object at 0x7f062e0bdb80, 0).wait(): got it pid 25118: MainThread: Condition(_thread.lock object at 0x7f062e0bdcc0, 0).notify(): no waiters pid 25118: MainThread: _MainThread(MainThread, stopped 139664631559936): waiting for other threads pid 25118: MainThread: Thread(Thread-1, started 139664516577024).join(): waiting until thread stops end of main -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
Changes by STINNER Victor victor.stin...@haypocalc.com: -- Removed message: http://bugs.python.org/msg148991 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
Changes by STINNER Victor victor.stin...@haypocalc.com: -- Removed message: http://bugs.python.org/msg148992 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
STINNER Victor victor.stin...@haypocalc.com added the comment: I removed my two previous message (msg148991 and msg148992), there were unrelated to this issue: the test hangs in debug mode in the IO module because of a deadleak in IO related to the fork... -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13549] Incorrect nested list comprehension documentation
New submission from Matt Long m...@crocodoc.com: The description of nesting list comprehensions in section 5.1.5 of the main Python tutorial (http://docs.python.org/tutorial/datastructures.html#nested-list-comprehensions) is misleading at best and arguably incorrect. Where it says To avoid apprehension when nesting list comprehensions, read from right to left. This is incorrect and conflicts directly with the comment at the bottom of PEP 202 (http://www.python.org/dev/peps/pep-0202/), which says the last index varies fastest. Take the following example: matrix = [[1,2],[3,4],[5,6]] my_list = [] for row in matrix: for number in row my_list.append(number) The current documentation would suggest I do the following to achieve the same result with list comprehensions since the for statements should be read from right to left: matrix = [[1,2],[3,4],[5,6]] my_list = [number for number in row for row in matrix] Running this code will result in an error. The correct form is: matrix = [[1,2],[3,4],[5,6]] [number for row in matrix for number in row] Clearly the nesting order only matters when the inner loop depends on the outer loop as in my example above. There is no such dependency in the documentation's example, which is why it is does not result in an Error. -- assignee: docs@python components: Documentation messages: 148994 nosy: docs@python, mattlong priority: normal severity: normal status: open title: Incorrect nested list comprehension documentation type: behavior versions: Python 2.6, Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13549 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13531] add test for defaultdict with non-callable first argument
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset a8deeb549e1a by Ezio Melotti in branch '2.7': #13531: add a test for defaultdict with a non-callable arg. Patch by Mike Cheng. http://hg.python.org/cpython/rev/a8deeb549e1a New changeset 17ceebc61b65 by Ezio Melotti in branch '3.2': #13531: add a test for defaultdict with a non-callable arg. Patch by Mike Cheng. http://hg.python.org/cpython/rev/17ceebc61b65 New changeset 4180308547d9 by Ezio Melotti in branch 'default': #13531: merge with 3.2. http://hg.python.org/cpython/rev/4180308547d9 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13531 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11870] test_3_join_in_forked_from_thread() of test_threading hangs 1 hour on x86 Ubuntu Shared 3.x
Charles-François Natali neolo...@free.fr added the comment: To debug this, we should probably make use of faulthandler (but not dump_tracebacks_later, since it creates a new thread). The way to go could be to make the parent process send a fatal signal to the child process if the latter takes too long to complete. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11870 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13531] add test for defaultdict with non-callable first argument
Ezio Melotti ezio.melo...@gmail.com added the comment: Committed, thanks for the report and the patch! For the record, this is related to https://bugs.pypy.org/issue953 -- resolution: - fixed stage: commit review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13531 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11051] system calls per import
Terry J. Reedy tjre...@udel.edu added the comment: I am a little puzzled by the patch. In logic, 'A and B' is equivalent to 'not A or not B'. But in the patch, -if (_Py_stat(filename, statbuf) == 0 /it exists */ -S_ISDIR(statbuf.st_mode)) /* it's a directory */ +if (_Py_stat(filename, statbuf) != 0 || S_ISDIR(statbuf.st_mode)) you seem to change to 'not A or B', without negating B. Is this intentional? What am I missing? Some subtle effect of lazy evaluation? Or an intentional change in the logic? -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11051 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11051] system calls per import
STINNER Victor victor.stin...@haypocalc.com added the comment: By the way, _Py_stat() can fail because of a Python error: -1 result is not handled in import.c :-( It may leak to the XXX undetected error message. -- nosy: +haypo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11051 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11051] system calls per import
Terry J. Reedy tjre...@udel.edu added the comment: OK, I gather from the comment added in the second patch that you intentionally changed the logic to restart the loop more often. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11051 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13550] Rewrite logging hack of the threading module
New submission from STINNER Victor victor.stin...@haypocalc.com: The threading module uses an hack to log actions to help debugging. The log depends on 3 flags: __debug__, threading._VERBOSE and a verbose attribute (each threading class has such attribute). By default, _note() is always called but does nothing: it checks the verbose attribute and return if the flag is False. Attached threading_note.patch only calls _note() if verbose is True to avoid a Python function call (which is slow in CPython). It avoids also a _Verbose parent class and pass the verbose flag to subobjects (e.g. Semaphore sets verbose argument of its Condition object). I don't think that it is really useful to be able to enable/disable logs on only one threading object, so it is maybe simpler to have only one global flag (instead of 3 flags): threading._VERBOSE. Attached threading_note_global.patch replaces _note() method by a function, remove _Verbose class and the _verbose attribute, and only call _note() if _VERBOSE is True. _VERBOSE and verbose arguments are undocumented and not tested, so I hope nobody relies on their API ;-) -- components: Library (Lib) files: threading_note.patch keywords: patch messages: 149001 nosy: haypo priority: normal severity: normal status: open title: Rewrite logging hack of the threading module versions: Python 3.3 Added file: http://bugs.python.org/file23869/threading_note.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13550] Rewrite logging hack of the threading module
Changes by STINNER Victor victor.stin...@haypocalc.com: Added file: http://bugs.python.org/file23870/threading_note_global.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13545] Pydoc3.2: TypeError: unorderable types
Peter Frauenglass python@everblue.info added the comment: The patch in msg148968 solves the issue for me. I'm running Linux, originally installed as Mint 9, though upgraded and modified incrementally until it's now kubuntu 11.10. I have the libc6 package version 2.13-20ubuntu5 installed. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13545 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13550] Rewrite logging hack of the threading module
Changes by STINNER Victor victor.stin...@haypocalc.com: Removed file: http://bugs.python.org/file23870/threading_note_global.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13550] Rewrite logging hack of the threading module
STINNER Victor victor.stin...@haypocalc.com added the comment: (threading_note_global.patch was completly wrong, here is the fixed version) -- Added file: http://bugs.python.org/file23871/threading_note_global.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13550 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11886] test_time.test_tzset() fails on x86 FreeBSD 7.2 3.x: AEST timezone called EST
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset c143e66e5efe by Victor Stinner in branch '3.2': Issue #11886: workaround an OS bug (time zone data) in test_time http://hg.python.org/cpython/rev/c143e66e5efe New changeset c7638be1e430 by Victor Stinner in branch 'default': (Merge 3.2) Issue #11886: workaround an OS bug (time zone data) in test_time http://hg.python.org/cpython/rev/c7638be1e430 New changeset 2bca2cee79a1 by Victor Stinner in branch '2.7': Issue #11886: workaround an OS bug (time zone data) in test_time http://hg.python.org/cpython/rev/2bca2cee79a1 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11886 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3786] _curses, _curses_panel _multiprocessing can't be build in 2.6b3 w/ SunStudio 12
STINNER Victor victor.stin...@haypocalc.com added the comment: I hacked setup.py and _cursesmodule.c to use XPG4 curses. It requires many hacks because it lacks functions like getattrs() or getsyx/setsyx, constant like KEY_MIN and KEY_MAX. It looks difficult to use this curses library. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3786 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13551] pulldom doesn't populate DOM tree
New submission from Achim Gaedke achim.gae...@physik.tu-darmstadt.de: Hi! I tried to use the more general xml.dom interface, no longer defaulting to minidom straight away (or using etree). The DOM tree gained with PullDOM seem to be incomplete. Here is the output of the program attached. $ python pulldom_test.py with pulldom (xml.dom.minidom.Document instance at 0xb722962c, []) with minidom (xml.dom.minidom.Document instance at 0xb72459ac, [DOM Text node u'\n', DOM Element: a at 0xb71cb74c, DOM Text node u'\n', DOM Element: b at 0xb71cb7ac, DOM Text node u'\n', DOM Element: c at 0xb71cb80c, DOM Text node u'\n']) I'd expect the same result for both ways of populating the minidom DOM implementation. Thanks Cheers, Achim -- components: XML files: pulldom_test.py messages: 149006 nosy: AchimGaedke priority: normal severity: normal status: open title: pulldom doesn't populate DOM tree type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file23872/pulldom_test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13552] Compilation issues of the curses module on OpenIndiana
New submission from STINNER Victor victor.stin...@haypocalc.com: The _curses module has two issues on OpenSolaris: - using the default curses library, mvwchgat() cannot be found and _curses module compilation fails - there is a XPG4 curses library. I tried to use it using various hacks in _cursesmodule.c and setup.py, but test_curses failed with a crash. - if the readline library (not the Python module) is linked to libncursesw, the compilation of the _curses module fails because cchar_t is not defined. I suppose that curses.h is the bytes library, not the ncursesw Unicode library. See issue #12567 for the ncursesw issue and issue #3786 for the mvwchgat() problem. The issue #3786 contains information about XPG4 curses and has a (non working) patch for the mvwchgat() issue. -- I opened a new issue because #12567 is more specific to Unicode, and #3786 talks about various issues (it is not specific to curses). -- components: Build messages: 149007 nosy: haypo, iandekit, jcea, mschmarck priority: normal severity: normal status: open title: Compilation issues of the curses module on OpenIndiana versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12567] curses implementation of Unicode is wrong in Python 3
STINNER Victor victor.stin...@haypocalc.com added the comment: I am still concerned about the compilation warning in OpenIndiana buildbots :-( I'm unable to reproduce the issue in my OpenIndiana VM: the compilaton of the _curses module fail, not because of Unicode, but because mvwchgat() function is missing = see the issue #3786. I don't know how to install ncursesw on OpenIndiana, I didn't find an official package using pkg search. curses issues on OpenIndiana are serious enough to have their own issue: I opened the issue #13552. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12567 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3786] _curses, _curses_panel _multiprocessing can't be build in 2.6b3 w/ SunStudio 12
STINNER Victor victor.stin...@haypocalc.com added the comment: I opened the issue #13552 to list all curses issues on OpenIndiana. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3786 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13552] Compilation issues of the curses module on OpenIndiana
STINNER Victor victor.stin...@haypocalc.com added the comment: curses_hacks.patch: various hacks to use the XPG4 curses on OpenIndiana. -- keywords: +patch nosy: +enchanter Added file: http://bugs.python.org/file23873/curses_hacks.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13552 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13551] pulldom doesn't populate DOM tree
Achim Gaedke achim.gae...@physik.tu-darmstadt.de added the comment: sorry, the output given before was generated with python2.7 changing the line xml.sax.parseString(xml_data, d_handler) to xml.sax.parseString(bytes(xml_data, utf-8), d_handler) makes it working for python 3.2, result the same: $ python3.2 pulldom_test.py with pulldom xml.dom.minidom.Document object at 0x9bf9f2c [] with minidom xml.dom.minidom.Document object at 0x9c2fccc [DOM Text node '\n', DOM Element: a at 0x9c3850c, DOM Text node '\n', DOM Element: b at 0x9c3856c, DOM Text node '\n', DOM Element: c at 0x9c385cc, DOM Text node '\n'] Both test were done on debian testing/wheezy. $ python3.2 -V Python 3.2.2rc1 $ python -V Python 2.7.2+ -- versions: +Python 2.7 Added file: http://bugs.python.org/file23874/pulldom_test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13551 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12567] curses implementation of Unicode is wrong in Python 3
STINNER Victor victor.stin...@haypocalc.com added the comment: The code has been commited. The remaining task is to fix OpenIndiana issues: see #13552. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12567 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue12567] curses implementation of Unicode is wrong in Python 3
Changes by STINNER Victor victor.stin...@haypocalc.com: -- resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue12567 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13553] Tkinter doesn't set proper application name
New submission from th9 rei4...@gmail.com: I want the app name to be displayed under the icon in Alt+Tab menu, but currently it only displays the className of the root, which by default is Tk. So in Gnome3 all Tkinter apps show up as Tk in the panel and in the Alt+Tab menu. It is possible to override that to some extent by giving className attribute to Tk(), but I don't know what the side effects are and it doesn't preserve capitalization of the name - the first letter is capital, but all others are small. Moreover, default title of the window is taken from the className by making first letter small and leaving the rest as given, so at the end nothing is as intended. E.g., if I give calssName=APP, the app is called App, but windows title is aPP. There should be a way to give this information, but I don't see it exposed anywhere and it is not correctly inferred from args[0] either. Example program attached. -- components: Tkinter files: tk_wm_test.py messages: 149013 nosy: th9 priority: normal severity: normal status: open title: Tkinter doesn't set proper application name type: behavior versions: Python 2.7, Python 3.2 Added file: http://bugs.python.org/file23875/tk_wm_test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13553 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13441] TestEnUSCollation.test_strxfrm() fails on Solaris
STINNER Victor victor.stin...@haypocalc.com added the comment: localeconv_wchar.c: test program to dump the thousands separator on a locale specified on the command line. I wrote this program to try to reproduce the hu_HU issue, but I cannot reproduce it on OpenIndiana. I only have UTF-8 locales on my OpenIndiana VM, whereas the issue looks to be specific to an ISO-8859-?? encoding (b'\xA0' is not decodable from UTF-8). -- Added file: http://bugs.python.org/file23876/localeconv_wchar.c ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13441 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13554] Tkinter doesn't use higher resolution app icon
New submission from th9 rei4...@gmail.com: 48x48 icons in Gnome3 show up blurry, but giving larger resolution (128 or 256) icon to Tkinter doesn't improve its appearance at all in the panel or Alt+Tab menu. I'm using 'photoimage' to get color icon. Giving two resolution icons in whatever order doesn't change anything - get blurry icon. Attached example script. It expects two PNG pictures (48x48 and 256x256) in the CWD and uses PIL to load them. -- components: Tkinter files: tk_wm_icon_test.py messages: 149015 nosy: th9 priority: normal severity: normal status: open title: Tkinter doesn't use higher resolution app icon type: behavior versions: Python 2.7 Added file: http://bugs.python.org/file23877/tk_wm_icon_test.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13554 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue7136] Idle File Menu Option Improvement
Roger Serwy roger.se...@gmail.com added the comment: This issue is mentioned as part of #13504 meta-issue. The attached patch extends Tal's original patch by also updating the help.txt documentation. -- nosy: +serwy Added file: http://bugs.python.org/file23878/issue7136.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue7136 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13319] IDLE: Menu accelerator conflict between Format and Options
Roger Serwy roger.se...@gmail.com added the comment: Attached is a patch to have Alt-i bring up the Options menu. -- keywords: +patch Added file: http://bugs.python.org/file23879/issue13319.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13319 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13502] Documentation for Event.wait return value is either wrong or incomplete
R. David Murray rdmur...@bitdance.com added the comment: On Wed, 07 Dec 2011 18:45:27 +, rep...@bugs.python.org wrote: ___ diff --git a/Doc/library/threading.rst b/Doc/library/threading.rst --- a/Doc/library/threading.rst +++ b/Doc/library/threading.rst @@ -804,8 +804,9 @@ floating point number specifying a timeout for the operation in seconds (or fractions thereof). - This method returns the internal flag on exit, so it will always return - ``True`` except if a timeout is given and the operation times out. + This method returns true if and only if the internal flag has been set to + true by another thread, so it will always return ``True`` except if a + timeout is given and the operation times out. This seems to imply that if the current thread previously set the event, the wait will return False, which is contradicted by the 'so' statement (which appears to be correct). --David -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13502 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13502] Documentation for Event.wait return value is either wrong or incomplete
Charles-François Natali neolo...@free.fr added the comment: This seems to imply that if the current thread previously set the event, the wait will return False, which is contradicted by the 'so' statement (which appears to be correct). You're probably referring to the another thread part... A suggestion ? I see you're a native speaker :-) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13502 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
