[issue14396] Popen wait() doesn't handle spurious wakeups
Gregory P. Smith g...@krypto.org added the comment: Thanks. I'll see that this fix gets into 2.7, 3.2 and 3.3. Out of curiosity, what Linux kernel version and glibc version were you using? I'm somewhat surprised that I haven't run into this before. :) -- assignee: - gregory.p.smith nosy: +gregory.p.smith -gps versions: +Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14396] Popen wait() doesn't handle spurious wakeups
Adin Scannell a...@scannell.ca added the comment: Kernel is 3.0.0-15-generic (I believe stock Ubuntu Oneric kernel). Version for glibc is Ubuntu EGLIBC 2.13-20ubuntu5. I'm working on figuring out the exact conditions under which it happens and creating a harness. I'll post it when I've got it. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14154] reimplement the bigmem test memory watchdog as a subprocess
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 53a2488605e3 by Charles-François Natali in branch 'default': Issue #14154: Reimplement the bigmem test memory watchdog as a subprocess. http://hg.python.org/cpython/rev/53a2488605e3 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14154 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14310] Socket duplication for windows
Kristján Valur Jónsson krist...@ccpgames.com added the comment: So, what is the consensus, does this go in or out? What about the share() and fromshare() functions, are people ok with that? -- versions: +Python 3.3 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14310 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14288] Make iterators pickleable
Kristján Valur Jónsson krist...@ccpgames.com added the comment: sbt, I will fix the api name. Any other objections then? Leave it as it is with the iter() trick? -- versions: +Python 3.3 -Python 3.4 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13902] Sporadic test_threading failure on FreeBSD 6.4 buildbot
Charles-François Natali neolo...@free.fr added the comment: And here's the full message: == FAIL: test_6_daemon_threads (test.test_threading.ThreadJoinOnShutdown) -- Traceback (most recent call last): File /usr/home/db3l/buildarea/3.2.bolen-freebsd/build/Lib/test/test_threading.py, line 667, in test_6_daemon_threads self.assertFalse(err) AssertionError: b'[46830 refs]\nThread 85d0600 has exited with leftover thread-specific data after 4 destructor iterations' is not false It's actually a bug in FreeBSD 7 pthread implementation, see http://lists.freebsd.org/pipermail/freebsd-threads/2009-June/004563.html The patch attached simply skips this test on FreeBSD 6 (like many other similar tests do). -- keywords: +patch nosy: +neologix Added file: http://bugs.python.org/file25010/freebsd_tls_spurious.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13902 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14396] Popen wait() doesn't handle spurious wakeups
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +neologix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14396 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
New submission from STINNER Victor victor.stin...@gmail.com: QueryPerformanceCounter() is not monotonic on a multiprocessor computer on Windows XP. Extract of its documentation: Remarks On a multiprocessor computer, it should not matter which processor is called. However, you can get different results on different processors due to bugs in the basic input/output system (BIOS) or the hardware abstraction layer (HAL). To specify processor affinity for a thread, use the SetThreadAffinityMask function. See also: http://bytes.com/topic/python/answers/527849-time-clock-going-backwards time.steady(strict-True) (or time.monotonic()? the function name is not decided yet :§)) should use GetTickCounter64(), or GetTickCounter(). GetTickCount64() was added to Windows Seven / Server 2008. GetTickCount() overflows after 49 days. QueryPerformanceCounter() has a better resolution than GetTickCount[64]() and so it's maybe better to keep it for time.steady(strict-False)? -- components: Library (Lib), Windows messages: 156690 nosy: haypo priority: normal severity: normal status: open title: Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14397 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
Changes by STINNER Victor victor.stin...@gmail.com: -- nosy: +brian.curtin, loewis, tim.golden ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14397 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue6634] sys.exit() called from threads other than the main one: undocumented behaviour
Antoine Pitrou pit...@free.fr added the comment: I don't see why this should be considered acceptable behavior. Why don't threads have their own ThreadExit exception, rather than overloading the use, and therefore, the meaning, of the SystemExit exception? As indicated by their names, sys.exit and the SystemExit exception should *only* be used to exit the entire system, not just a thread! I agree the situation isn't optimal. However, fixing this would also break compatibility with any application that uses sys.exit() in a thread and expects it to exit the thread, not the whole process. So we're kind of stuck with it. -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6634 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14349] The documentation of 'dis' doesn't describe MAKE_FUNCTION correctly
Georg Brandl ge...@python.org added the comment: Looks good to me. -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13902] Sporadic test_threading failure on FreeBSD 6.4 buildbot
Nadeem Vawda nadeem.va...@gmail.com added the comment: Patch looks good to me. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13902 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
Changes by Yury Selivanov yseliva...@gmail.com: -- nosy: +Yury.Selivanov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14397 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14288] Make iterators pickleable
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
Yury Selivanov yseliva...@gmail.com added the comment: I vote for adding just one function to the 'time' module: monotonic(), which should exist only if the host OS support it. And I don't see the point of having 'steady()' at all. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14397 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
Martin v. Löwis mar...@v.loewis.de added the comment: A monotonic clock is not suitable for measuring durations, as it may still jump forward. A steady clock will not. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14397 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14364] Argparse incorrectly handles '--'
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14364 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14365] argparse: subparsers, argument abbreviations and ambiguous option
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo stage: - test needed versions: +Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14365 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14367] try/except block in ismethoddescriptor() in inspect.py, so that pydoc works with pygame in Python 3.2
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14367 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14361] No link to issue tracker on Python home page
Daniel Swanson popcorn.tomato.d...@gmail.com added the comment: i don't remember -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14361 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9995] setup.py register sdist upload requires pass to be saved
Florent Xicluna florent.xicl...@gmail.com added the comment: If someone else is looking for the PyPI SSH support, it's there. http://pypi.python.org/pypi/pypissh (I did not find it mentioned in the tutorial) Thanks Martin. -- nosy: +flox ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9995 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4331] Can't use _functools.partial() created function as method
Changes by Matt Joiner anacro...@gmail.com: -- nosy: +anacrolix ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4331 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
New submission from Laurent Gautier lgaut...@gmail.com: The call ends with: Objects/stringobject.c:3884: bad argument to internal function sys.version: '2.7.2 (default, Jun 13 2011, 15:14:50) \n[GCC 4.4.5]' (on 64bit Linux) -- messages: 156698 nosy: Laurent.Gautier priority: normal severity: normal status: open title: bz2.BZ2DEcompressor.decompress fail on large files type: crash versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14399] zipfile and creat/update comment
New submission from Cassaigne anthony.cassai...@gmail.com:
I want to update or create a comment to zip file.
For instance, I have test.zip file.
I'm using these statement to create a comment :
from zipfile import ZipFile
z=ZipFile('test.zip','a')
z.comment='Create a new comment'
z.close()
After to ran this script, the zip file test.zip doesn't including the new
comment !
I can have the expected behavior when I add a new file inner zip archive.
--
components: Library (Lib)
files: bug_zipfile_comment.py
messages: 156699
nosy: acassaigne
priority: normal
severity: normal
status: open
title: zipfile and creat/update comment
type: behavior
versions: Python 2.7
Added file: http://bugs.python.org/file25011/bug_zipfile_comment.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14399
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14400] Typo in cporting.rst
New submission from Dionysios Kalofonos peite...@gmail.com: A typo (see attached file). -- assignee: docs@python components: Documentation files: typo.diff keywords: patch messages: 156700 nosy: dk, docs@python priority: normal severity: normal status: open title: Typo in cporting.rst versions: Python 2.7 Added file: http://bugs.python.org/file25012/typo.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14400 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14400] Typo in cporting.rst
Changes by Dionysios Kalofonos peite...@gmail.com: -- versions: +Python 3.1, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14400 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Martin v. Löwis mar...@v.loewis.de added the comment: I can't reproduce this. Can you please provide a test script along with input data that allows us to reproduce this error? -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14400] Typo in cporting.rst
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset e0e28695f11b by Martin v. Löwis in branch '2.7': Issue #14400: Fix typo. http://hg.python.org/cpython/rev/e0e28695f11b -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14400 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14400] Typo in cporting.rst
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset ff679f22682b by Martin v. Löwis in branch '3.2': Issue #14400: Fix typo. http://hg.python.org/cpython/rev/ff679f22682b -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14400 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14400] Typo in cporting.rst
Martin v. Löwis mar...@v.loewis.de added the comment: Thanks for the patch. -- nosy: +loewis resolution: - fixed status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14400 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Laurent Gautier lgaut...@gmail.com added the comment: Wow! Quick follow-up. The data file is about 1.6Gb. Is there a preferred way to pass it on (I suspect that the bug tracker is not the preferred way). The code goes like: import bz2 f = file(foobar.bz2, mode=rb) src_buf = f.read() decomp = bz2.BZ2Decompressor() tmp = decomp.decompress(src_buf) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14065] Element should support cyclic GC
Eli Bendersky eli...@gmail.com added the comment: Find attached a patch. Added cyclic GC support to Element objects. Also added tests that verify that cycles involving Element objects are being collected. I'd really appreciate a review on this, since this is the first time I have to explicitly deal with cyclic GC from C extensions. -- keywords: +patch stage: needs patch - patch review Added file: http://bugs.python.org/file25013/issue14065.1.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14065 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14349] The documentation of 'dis' doesn't describe MAKE_FUNCTION correctly
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 242d3f8e8c50 by Eli Bendersky in branch 'default': Issue #14349: Fix the doc of the MAKE_FUNCTION opcode in Doc/library/dis.rst to http://hg.python.org/cpython/rev/242d3f8e8c50 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14349] The documentation of 'dis' doesn't describe MAKE_FUNCTION correctly
Changes by Eli Bendersky eli...@gmail.com: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14349 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14401] Typos in curses.rst
New submission from Dionysios Kalofonos peite...@gmail.com: Typos (see attached file). -- assignee: docs@python components: Documentation files: curses.diff keywords: patch messages: 156708 nosy: dk, docs@python priority: normal severity: normal status: open title: Typos in curses.rst versions: Python 2.7, Python 3.1, Python 3.3 Added file: http://bugs.python.org/file25014/curses.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14401 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Nadeem Vawda nadeem.va...@gmail.com added the comment: I have been able to reproduce it; see attached script. It happens for inputs of 2GB (decompressed), but not for ones of 1GB. It seems that bz2module.c doesn't guard against 32-bit overflows when handling the size of the decompressed data. This affects both the BZ2Decompressor object's decompress() method, and the module-level decompress() function. All python versions prior to 3.3 are affected. -- assignee: - nadeem.vawda components: +Extension Modules nosy: +nadeem.vawda stage: - needs patch Added file: http://bugs.python.org/file25015/testbz2.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Nadeem Vawda nadeem.va...@gmail.com added the comment: (the contents of the input file don't matter; I just pulled out a bunch of zeros from /dev/zero and compressed them with bzip2.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Changes by Nadeem Vawda nadeem.va...@gmail.com: -- versions: +Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Nadeem Vawda nadeem.va...@gmail.com added the comment: This should be fixed for 2.7.3. I'll have a patch ready in the next day or two. -- nosy: +benjamin.peterson, georg.brandl priority: normal - release blocker ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4331] Can't use _functools.partial() created function as method
Matt Joiner anacro...@gmail.com added the comment: I've attached a patch that implements the descriptor protocol for functools.partial with minimum changes. -- Added file: http://bugs.python.org/file25016/functools.partial-descrget.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4331 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Benjamin Peterson benja...@python.org added the comment: This isn't a regression, is it? If it's not, I don't think it's essential to get into 2.7.3. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Nadeem Vawda nadeem.va...@gmail.com added the comment: No, it's been around since at least 2.6. I wasn't really sure what the protocol was for bugs found during the RC process. It'd be nice to get a fix for this into 2.7.3 (and 3.2.3), but it's not urgent. -- priority: release blocker - normal ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Martin v. Löwis mar...@v.loewis.de added the comment: Nadeem: the final release candidate of 2.7.3 was already made. Any further change would require another release candidate, which in turn would delay the release further. This has to wait for 2.7.4. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13902] Sporadic test_threading failure on FreeBSD 6.4 buildbot
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 2456e4e69cd0 by Charles-François Natali in branch '3.2': Issue #13902: Fix a random test_threading failure on FreeBSD 6 buildbots (due http://hg.python.org/cpython/rev/2456e4e69cd0 New changeset c1191cbc7b37 by Charles-François Natali in branch 'default': Issue #13902: Fix a random test_threading failure on FreeBSD 6 buildbots (due http://hg.python.org/cpython/rev/c1191cbc7b37 -- nosy: +python-dev ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13902 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14154] reimplement the bigmem test memory watchdog as a subprocess
Changes by Charles-François Natali neolo...@free.fr: -- resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14154 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14398] bz2.BZ2DEcompressor.decompress fail on large files
Nadeem Vawda nadeem.va...@gmail.com added the comment: That's fine by me, then. Sorry for the confusion. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14398 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14397] Use GetTickCount/GetTickCount64 instead of QueryPerformanceCounter for monotonic clock
Yury Selivanov yseliva...@gmail.com added the comment: A monotonic clock is not suitable for measuring durations, as it may still jump forward. A steady clock will not. Well, Victor's implementation of 'steady()' is just a tiny wrapper, which uses 'monotonic()' or 'time()' if the former is not available. Hence 'steady()' is a misleading name. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14397 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14402] Notice PayPaI : Your account was accesed by a third party.
Changes by Guido van Rossum gu...@python.org: -- resolution: - invalid status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14402 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14288] Make iterators pickleable
Raymond Hettinger raymond.hettin...@gmail.com added the comment: Has python-dev discussion been launched? It is far from clear that this is worth doing. Pickling runtime structures may be a normal use case for Stackless but isn't a normal use case for regular Python. Also, it seems pointless to start down this path because it will always be incomplete (i.e. pickling running generators, or socket streams, etc). It also seems to be at odds with the normal use case for passing around partially consumed iterators -- the laziness and memory friendliness is a desired feature; however, the patch pickles some iterators (such as dicts) by running them to completion and storing *all* of the results that would have been returned. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14350] Strange Exception from copying an iterator
Terry J. Reedy tjre...@udel.edu added the comment: Title corrected. Non-iterator iterables are usually easy to copy. I think this is in the category of don't do that ;-) I believe the idea of making iterators copyable has been rejected on one of the lists because it is probably not possible in general. Tee consumes indefinite and unbounded space. Its use should be explicit. If a function needs to iterate more than once with an input iterable, it should explicitly do list(iterator) for iterator inputs. See Raymond's comments, such as msg156720 in #14288. So I suspect that raising an error for copy.copy(iter([])) is correct. The error message amounts to saying make a new instance with the class constructor. That is usually correct when copy is not possible, but not in this case. ListIterator.__new__ is the inherited object.__new__. It appears that ListIterators can only be constructed by list.__iter__. But I doubt that the code that raises the error message can know that. But perhaps the error message can be improved anyway. -- nosy: +alexandre.vassalotti, rhettinger, terry.reedy stage: - needs patch title: Strange Exception from copying an iterable - Strange Exception from copying an iterator ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14350 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14288] Make iterators pickleable
Martin v. Löwis mar...@v.loewis.de added the comment: I think the worth doing argument doesn't really hold, given that it's done. The question at hand really is a) is the patch correct? b) can we commit to maintaining it, even as things around it may change? I'm not bothered with the patch being potentially incomplete: anybody wishing to pickle more things should contribute patches for that. As for a), I think we should give people some time to review, and then wait for beta releases to discover issues. If this is a rarely-used feature, the world won't end if it has bugs. As for b), I think the main issue is forward compatibility: will pickles created by 3.3 still be readable by future versions? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14288] Make iterators pickleable
Michael Foord mich...@voidspace.org.uk added the comment: Yes there was a discussion on python-dev. Various people spoke in favour, no-one against: http://mail.python.org/pipermail/python-dev/2012-March/117566.html -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14361] No link to issue tracker on Python home page
Terry J. Reedy tjre...@udel.edu added the comment: This issue seems 'off-topic' in that core developers do not control the main site and cannot patch it. My understanding is that that is why the dev guide was separated from the main site (so we could patch it). On the other hand, we can suggest changes like anyone else. We (core devs) do not want this tracker used for everyday support requests. They are a minor but not non-existent problem. They will get quicker and ofter better responses on other, more appropriate forums. In the future, when I suggest 'report that on the tracker' on python-list, I will try to remember to include 'at bugs.python.org'. I do think there should be a Reporting Bugs page (or section) and link somewhere on the site, but not on the front page. Apparently there already is something like that. A 'Getting Involved' page is a traditional place. That gateway would ideally be the first hit for a 'report bug' or 'bug tracker' site search. However, even now, the first hit summary for either search gives the necessary information in spite of the strange doc link. Reporting Bugs in Python — Python v2.6.5c2 documentation www.python.org/doc//current/bugs.html Mar 13, 2010 – Bug reports should be submitted via the Python Bug Tracker (http://bugs.python.org/). The bug tracker offers a Web form which allows pertinent ... Perhaps neither Steven or Daniel noticed the 'quiet' search box. I would like to see a label that specifies what is searched. See Advanced Search for possibilities. It could also be moved to the center to better attract attention. Stephen, you are free to send a suggestion to webmas...@python.org. Since you asked for input here, I would hope you would incorporate it ;-). You can also close this when you think discussion has run out. -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14361 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14374] Compiling Python 2.7.2 on HP11i PA-RISC ends with segmentation fault in Python executable
Terry J. Reedy tjre...@udel.edu added the comment: This does not seem to clearly be a bug in the core codebase. An enquiry on python-list or maybe even stackoverflow might get a response from someone with HP11i PA-RISC experience. -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14374 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14376] sys.exit documents argument as integer but actually requires subtype of int
Terry J. Reedy tjre...@udel.edu added the comment: Patch in first message; patch file needed. I don't know if sys.exit is actually tested. This is really 2.7 specific. -- keywords: +patch nosy: +terry.reedy stage: - test needed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14376 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14391] misc TYPO in argparse.Action docstring
Terry J. Reedy tjre...@udel.edu added the comment: The patch, to an unspecified version of 2.7, changes 'str' to 'string', so I presume that is what you meant. The current repository code already says 'string' for 2.7, 3.2, and 3.3. This is what you should see in the current release candidates, including 2.7.3rc2 -- assignee: - docs@python components: +Documentation nosy: +bethard, docs@python, terry.reedy resolution: - out of date stage: - patch review status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14391 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14392] type=bool doesn't raise error in argparse.Action
Terry J. Reedy tjre...@udel.edu added the comment: This change maked the error message wrong if bool is rejected. -- nosy: +bethard, terry.reedy stage: - test needed type: - behavior ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14392 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14392] type=bool doesn't raise error in argparse.Action
Terry J. Reedy tjre...@udel.edu added the comment: The corresponding current code in 3.2 and 3.3 is the same. -- versions: +Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14392 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14393] Incorporate Guide to Magic Methods?
Terry J. Reedy tjre...@udel.edu added the comment: If one searches for the informal name 'Python magic methods', RafeKettler's doc and 3. Data model — Python v2.7.2 documentation come in 1,2. Given that the latter does not even contain the word 'magic', that means that is actually ranks higher in some real sense. Suggestion: we should do a bit of SEO and add the informal name to that page (and 3.4). Then either might come in first for such inquiries. If one searches for the official name 'Python special methods', then our Chapter 3 comes in first and RafeK's doc 9th. The 2.5.2 version of 3.4 Special method names comes in second. This points to a second problem with google rank: we have several versions of the docs indexed, so links to our docs are scattered among them, and none rank as high as they really should. I glanced at the git doc and it seems to largely duplicate the info in the docs already. So it should not be just 'incorporated'. Dirkjan: if you have any specific suggestions for doc improvement, regardless of inspiration, please give them. If not, I think this issue should be closed. -- nosy: +terry.reedy ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14393 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue14288] Make iterators pickleable
Raymond Hettinger raymond.hettin...@gmail.com added the comment: Michael, thanks for the link. The email was clearer about its rationale than was listed here. When this patch gets applied, any discussion of it in the docs should be clear that generators aren't included and that pickling things like dict iterators entail running the iterator to completion and storing all of the results in a list. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14288 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
