[issue13884] IDLE 2.6.5 Recent Files undocks

Terry J. Reedy added the comment: IDLE has tear-off menus. From Help/IDLE Help: "Click on the dotted line at the top of a menu to "tear it off": a separate window containing the menu is created." This is a feature, not a bug. On 3.2.2, Win7, the Recent Files sub-menu cannot be torn off unless a

[issue13703] Hash collision security issue

Gregory P. Smith added the comment: >> But using non-__builtin__.str objects (such as UserString) would expose the >> user to an attack? > > Not necessarily: only if they use these strings as dictionary keys, and only > if they do so in contexts where arbitrary user input is consumed. In these >

[issue6210] Exception Chaining missing method for suppressing context

Steven D'Aprano added the comment: [...] My comment has been overtaken by additional comments by Nick on the Python-Dev list. -- ___ Python tracker ___

[issue13847] Catch time(), ftime(), localtime() and clock() errors

STINNER Victor added the comment: There is still an error on Windows: == FAIL: test_localtime_failure (test.test_time.TimeTestCase) -- Traceback (most recent c

[issue6210] Exception Chaining missing method for suppressing context

Steven D'Aprano added the comment: Nick Coghlan wrote: > Nick Coghlan added the comment: > > 1. Any syntax change requires a PEP (and, IMO, any such PEP for this issue > should get rejected: I don't consider this an important enough feature to > deserve dedicated syntax. Others disagree, which

[issue6210] Exception Chaining missing method for suppressing context

Ethan Furman added the comment: Nick Coghlan wrote: > 1. Any syntax change requires a PEP PEP is on python-dev. -- ___ Python tracker ___ ___

[issue6210] Exception Chaining missing method for suppressing context

Ethan Furman added the comment: > 1. Any syntax change requires a PEP (and, IMO, any such PEP for this issue > should get rejected: I don't consider this an important enough feature to > deserve dedicated syntax. Others disagree, which is one of the reasons why a > PEP is needed. The other, m

[issue13703] Hash collision security issue

Martin v. Löwis added the comment: > If I your read patch correctly, collisions will produce additional > allocations of one distinct PyObject (i.e. AVL node) per colliding key. That's correct. > That's a pretty massive change in memory consumption for string dicts > (and also in memory fragme

[issue13651] Improve redirection in urllib

tom kel added the comment: I changed the patch and made it a little bit better. -- versions: +Python 3.1, Python 3.4 -Python 2.7 Added file: http://bugs.python.org/file24334/2012-1-26.diff ___ Python tracker _

[issue6210] Exception Chaining missing method for suppressing context

Nick Coghlan added the comment: 1. Any syntax change requires a PEP (and, IMO, any such PEP for this issue should get rejected: I don't consider this an important enough feature to deserve dedicated syntax. Others disagree, which is one of the reasons why a PEP is needed. The other, more impo

[issue13703] Hash collision security issue

Antoine Pitrou added the comment: > > There were three discussed issues with it: > > > > a) Code assuming a stable ordering to dictionaries > > b) Code assuming hashes were stable across runs. > > c) Code reimplementing the hashing algorithm of a core datatype that is now > > randomized. > > >

[issue13847] Catch time(), ftime(), localtime() and clock() errors

STINNER Victor added the comment: The issue should be done with the last commit. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue13847] Catch time(), ftime(), localtime() and clock() errors

Roundup Robot added the comment: New changeset 856f0864437a by Victor Stinner in branch 'default': Issue #13847: Make test_localtime_failure() more robust http://hg.python.org/cpython/rev/856f0864437a -- ___ Python tracker

[issue13884] IDLE 2.6.5 Recent Files undocks

Ezio Melotti added the comment: Could you try with IDLE 2.7/3.2? -- nosy: +ezio.melotti, terry.reedy ___ Python tracker ___ ___ Pytho

[issue13847] Catch time(), ftime(), localtime() and clock() errors

Roundup Robot added the comment: New changeset 516d42a6e518 by Victor Stinner in branch 'default': Issue #13847: Fix test_mktime(), time.localtime() now raises OSError http://hg.python.org/cpython/rev/516d42a6e518 -- ___ Python tracker

[issue13847] Catch time(), ftime(), localtime() and clock() errors

STINNER Victor added the comment: I added tests on localtime() and clock(). I read more carefully time(), ftime() and gettimeofday() manpage: it is not possible that they fail if the argument is an invalid pointer, the current code is correct. I don't want to backport changes because they ar

[issue13703] Hash collision security issue

Martin v. Löwis added the comment: > I'm sorry then, but I'm a little confused. I think we pretty clearly > established earlier that requiring users to make changes anywhere they > stored user data would be dangerous, because these locations are often in > libraries or other places where the co

[issue13884] IDLE 2.6.5 Recent Files undocks

New submission from Tim McGreevy : When selecting from menu: File --> Recent Files the 'Recent Files' dropdown list undocks from the IDLE gui / File dropdown list. Even after selecting a past file, it remains open until closed manually. Ubuntu LUCID amd64 IDLE 2.6.5 TK version 8.5 All installe

[issue13847] Catch time(), ftime(), localtime() and clock() errors

Roundup Robot added the comment: New changeset 94b7eb09d0b3 by Victor Stinner in branch 'default': Issue #13847: time.clock() now raises a RuntimeError if the processor time used http://hg.python.org/cpython/rev/94b7eb09d0b3 -- ___ Python tracker

[issue13883] PYTHONCASEOK docs mistakenly says it is limited to Windows

Changes by Brett Cannon : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue13883] PYTHONCASEOK docs mistakenly says it is limited to Windows

Roundup Robot added the comment: New changeset 524795e8abe1 by Brett Cannon in branch '3.2': Issue #13883: Document all platforms PYTHONCASEOK works on. http://hg.python.org/cpython/rev/524795e8abe1 New changeset 0f00010c88f0 by Brett Cannon in branch 'default': Issue #13883: PYTHONCASEOK also

[issue13873] SIGBUS in test_zlib on Debian bigmem buildbot

Torsten Landschoff added the comment: I tried to reproduce this crash on my desktop system. AMD64, 8 GB RAM (only) and on Debian unstable from today. Testing the exact same Python version (hg update d2cf8a34ddf90fb1bc8938de0f736694e61f73fa) the test passes just fine here... -- nosy: +t

[issue13703] Hash collision security issue

Alex Gaynor added the comment: I'm sorry then, but I'm a little confused. I think we pretty clearly established earlier that requiring users to make changes anywhere they stored user data would be dangerous, because these locations are often in libraries or other places where the code creating

[issue6210] Exception Chaining missing method for suppressing context

Ethan Furman added the comment: I went with raise ... from None instead of raise as ... because there seemed to me more support for 'from None' on python-dev, possible confusion with 'raise as', and 'from None' follows the existing systax of raise SomeError() from SomeOtherErr

[issue13847] Catch time(), ftime(), localtime() and clock() errors

Roundup Robot added the comment: New changeset 9ee4a104e33d by Victor Stinner in branch 'default': Issue #13847: time.localtime() and time.gmtime() now raise an OSError instead http://hg.python.org/cpython/rev/9ee4a104e33d -- nosy: +python-dev ___ Py

[issue13703] Hash collision security issue

Martin v. Löwis added the comment: > But using non-__builtin__.str objects (such as UserString) would expose the > user to an attack? Not necessarily: only if they use these strings as dictionary keys, and only if they do so in contexts where arbitrary user input is consumed. In these cases, us

[issue6210] Exception Chaining missing method for suppressing context

Ethan Furman added the comment: Okay, here is a patch implementing the 'raise ... from None' method. All critiques appreciated (especially if they include links to learn from!). -- keywords: +patch Added file: http://bugs.python.org/file24332/raise_from_none.diff _

[issue13703] Hash collision security issue

Alex Gaynor added the comment: On Thu, Jan 26, 2012 at 5:42 PM, Martin v. Löwis wrote: > > Martin v. Löwis added the comment: > > > What happens if, instead of putting strings in a dictionary directly, I > > have them wrapped in something. For example, the classes Antoine and I > > pasted ear

[issue13703] Hash collision security issue

Martin v. Löwis added the comment: > What happens if, instead of putting strings in a dictionary directly, I > have them wrapped in something. For example, the classes Antoine and I > pasted early. These define hash and equal as being strings, but don't have > an ordering. As Dave has analyse

[issue13703] Hash collision security issue

Martin v. Löwis added the comment: > as soon as any key insertion or lookup occurs where the key isn't > exactly one of the correct types, the dict flattens any AVL trees back > into the regular flat representation (and switches to lookdict for > ma_lookup), analogous to the existing ma_lookup t

[issue13666] datetime documentation typos

Stephen Kelly added the comment: There are actually other bugs in the same code example: ... def __init__(self): # DST starts last Sunday in March ... d = datetime(dt.year, 4, 1) # ends last Sunday in October ... self.dston = d - timedelta(days=d.weekday() + 1) ...

[issue13703] Hash collision security issue

Dave Malcolm added the comment: On Thu, 2012-01-26 at 21:04 +, Alex Gaynor wrote: > Alex Gaynor added the comment: > > On Thu, Jan 26, 2012 at 4:00 PM, Martin v. Löwis > wrote: > > > > > Martin v. Löwis added the comment: > > > > I'd like to propose an entirely different approach: use A

[issue13845] Use GetSystemTimeAsFileTime() to get a resolution of 100 ns on Windows

STINNER Victor added the comment: Using the patch of #13882, I realize that time.time() has a resolution of 1 millisecond (10^-3) and not of a microsecond (10^-6) on Windows! Windows doesn't provide gettimeofday(). Using GetSystemTimeAsFileTime() would provide a much better resolution! -

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

STINNER Victor added the comment: Windows code (win32_clock) was wrong in time_decimal-2.patch: it is fixed in patch version 3. Some tests on Windows made me realize that time.time() has a resolution of 1 millisecond (10^-3) and not of a microsecond (10^-6) on Windows! It is time to use GetS

[issue13883] PYTHONCASEOK docs mistakenly says it is limited to Windows

New submission from Brett Cannon : The docs for PYTHONCASEOK say it is limited to Windows, but in actuality in Python 3.x it applies to both Windows (including cygwin) and OS X. On Python 2.7 it applies to those plus RISCOS OS/2. -- assignee: docs@python components: Documentation messa

[issue13703] Hash collision security issue

Alex Gaynor added the comment: On Thu, Jan 26, 2012 at 4:00 PM, Martin v. Löwis wrote: > > Martin v. Löwis added the comment: > > I'd like to propose an entirely different approach: use AVL trees for > colliding strings, for dictionaries containing only unicode or byte strings. > > A prototype

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

STINNER Victor added the comment: Some examples of the API: $ ./python Python 3.3.0a0 (default:52f68c95e025+, Jan 26 2012, 21:54:31) >>> import time >>> time.time() 1327611705.948446 >>> time.time('decimal') Decimal('1327611708.988419') >>> t1=time.time('decimal'); t2=time.time('decimal'); t2

[issue13882] Add format argument for time.time(), time.clock(), ... to get a timestamp as a Decimal object

New submission from STINNER Victor : Attached patch adds an optional format argument to time.time(), time.clock(), time.wallclock(), time.clock_gettime() and time.clock_getres() to get the timestamp as a different format. By default, the float type is still used, but it will be possible to pas

[issue13703] Hash collision security issue

Martin v. Löwis added the comment: I'd like to propose an entirely different approach: use AVL trees for colliding strings, for dictionaries containing only unicode or byte strings. A prototype for this is in http://hg.python.org/sandbox/loewis/branches#avl It is not fully working yet, but I'm

[issue13881] Stream encoder for zlib_codec doesn't use the incremental encoder

New submission from Andrew McNabb : The stream encoder for the zlib_codec doesn't use the incremental encoder, so it has limited usefulness in practice. This is easiest to show with an example. Here is the behavior with the stream encoder: >>> filelike = io.BytesIO() >>> wrapped = codecs.getwr

[issue13455] Reorganize tracker docs in the devguide

Terry J. Reedy added the comment: Antoine, what reference other than the devguide are you referring to? If you keep info I need out of the devguide, where am I supposed to find it? python.org/dev now redirects to python.org/devguide. -- ___ Python

[issue13880] pydoc -k throws "AssertionError: distutils has already been patched by "

New submission from __KFL__ : Pydoc fails on the following exception. There is a mail discussing it: http://mail.python.org/pipermail/python-list/2009-December/1230790.html C:\Python27\Lib>pydoc -k file ... ... Traceback (most recent call last): File "C:\Python27\Lib\pydoc.py", line 2338, in

[issue10580] Installer sentence in bold

Boštjan Mejak added the comment: After more than a year the patch is finally made. Can someone please applies this patch and closes this issue report? Thanks. -- keywords: +patch versions: +Python 3.3 Added file: http://bugs.python.org/file24329/issue10580.diff ___

[issue13874] test_faulthandler: read_null test fails with current clang

STINNER Victor added the comment: There was a similar bug which was declared as a vulnerability in the Linux kernel: http://isc.sans.edu/diary.html?storyid=6820 GCC has an option to disable this optimization: -fno-delete-null-pointer-checks. -- ___

[issue13876] Sporadic failure in test_socket

Changes by Ross Lagerwall : -- nosy: +rosslagerwall ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue13879] Argparse does not support subparser aliases in 2.7

New submission from Tim Willis : Argparse documentation in 2.7 indicates support for an 'aliases' kwarg. (Fourth example down from http://docs.python.org/dev/library/argparse.html#sub-commands) While aliases work as expected in 3.2, use in 2.7 results in TypeError: __init__() got an unexpect

[issue13878] test_sched failures on Windows buildbot

Nadeem Vawda added the comment: Oops, those links should be: http://www.python.org/dev/buildbot/all/builders/x86%20XP-5%203.x/builds/4072/steps/test/logs/stdio and: http://www.python.org/dev/buildbot/all/builders/x86%20XP-5%203.x/builds/4062/steps/test/logs/stdio -- _

[issue13878] test_sched failures on Windows buildbot

New submission from Nadeem Vawda : http://www.python.org/dev/buildbot/all/builders/x86%20XP-5%203.x/builds/4072/steps/test/logs/stdio: FAIL: test_enter (test.test_sched.TestCase) -- Traceback (most recent call last):

[issue13877] segfault when running smtplib example

Amaury Forgeot d'Arc added the comment: Do you have a more complete traceback by any chance? Also, does the "New Thread..." message indicate that a new thread is created? Why? This is not what I see here. -- nosy: +amaury.forgeotdarc ___ Python tr

[issue13877] segfault when running smtplib example

New submission from Jon Bringhurst : I just ran into this while using the smtplib example on: 2.6 (r26:66714, Jan 17 2012, 11:02:11) GCC 4.1.2 20080704 (Red Hat 4.1.2-44) Running the program simply gives a "Segmentation Fault (core dumped)" Running it under gdb... [Thread debugging using libt

[issue8828] Atomic function to rename a file

Antoine Pitrou added the comment: Here is a patch adding os.replace(). -- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file24328/osreplace.patch ___ Python tracker

[issue1003195] segfault when running smtplib example

Changes by Jon Bringhurst : -- type: -> crash versions: +Python 2.6 -Python 2.2 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue1003195] segfault when running smtplib example

Jon Bringhurst added the comment: I just ran into this while using the smtplib example on: 2.6 (r26:66714, Jan 17 2012, 11:02:11) GCC 4.1.2 20080704 (Red Hat 4.1.2-44) Running the program simply gives a "Segmentation Fault (core dumped)" Running it under gdb... [Thread debugging using libthr

[issue13875] cmd: no user documentation

R. David Murray added the comment: You can feed a cmd driven interface from stdin or via cmd.onecmd. However, I agree that the intended and primary use case is interactive. There wouldn't be much point in using cmd if the primary intent of your program wasn't interactive. -- __

[issue13840] create_string_buffer rejects str init_or_size parameter

Meador Inge added the comment: I just fixed the docs and error message for now. I might revisit the ASCII decoding later. Thanks for the bug report Vincent. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed

[issue13840] create_string_buffer rejects str init_or_size parameter

Roundup Robot added the comment: New changeset be9d02536a81 by Meador Inge in branch '3.2': - Issue #13840: Fix ctypes.create_string_buffer exception message and docs. http://hg.python.org/cpython/rev/be9d02536a81 New changeset 52f68c95e025 by Meador Inge in branch 'default': - Issue #13840: Fi

[issue13875] cmd: no user documentation

anatoly techtonik added the comment: What do you mean by saying it is not limited for interactive use? I thought it is used to provide command prompt for typing commands. What other use cases does it support? -- status: pending -> open ___ Python t

[issue13875] cmd: no user documentation

R. David Murray added the comment: Well, since it isn't limited to interactive use, I don't think 'interactive' is missing. MOTW links are a more global issue that was discussion on python-dev (I forget the outcome, but I think it was "no"). I don't see anything that needs done here, but if

[issue13876] Sporadic failure in test_socket

New submission from Nadeem Vawda : When running the test suite, I occasionally get the following failure: ERROR: testRecvmsgEOF (test.test_socket.RecvmsgSCTPStreamTest) -- Traceback (most recent call last): Fil

[issue13874] test_faulthandler: read_null test fails with current clang

Stefan Krah added the comment: STINNER Victor wrote: > Can you try x = (int *)1; instead of x = NULL; ? This works. - I must say that I find this new behavior of clang slightly dangerous... -- ___ Python tracker

[issue13875] cmd: no user documentation

New submission from anatoly techtonik : http://docs.python.org/library/cmd.html# Documentation for cmd module is poor to explain the value of this module to users. Intro is too abstract - phrase "simple framework for writing line-oriented command interpreters" doesn't mean much. Perhaps word

[issue13863] import.c sometimes generates incorrect timestamps on Windows + NTFS

Antoine Pitrou added the comment: Hmm, interesting. This is exactly what happened recently when debugging pyc timestamp issues under Windows: http://www.python.org/dev/buildbot/all/builders/x86%20Windows7%202.7/builds/1204/steps/test/logs/stdio Some decoding of the above crash: - the test woul

[issue13863] import.c sometimes generates incorrect timestamps on Windows + NTFS

Changes by Antoine Pitrou : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13874] test_faulthandler: read_null test fails with current clang

STINNER Victor added the comment: Can you try x = (int *)1; instead of x = NULL; ? -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue13874] test_faulthandler: read_null test fails with current clang

New submission from Stefan Krah : In non-debug mode the read_null test fails with clang-3.0: == FAIL: test_disable (test.test_faulthandler.FaultHandlerTests) --

[issue13873] SIGBUS in test_zlib on Debian bigmem buildbot

New submission from Nadeem Vawda : http://www.python.org/dev/buildbot/all/builders/AMD64%20debian%20bigmem%203.x/builds/58/steps/test/logs/stdio -- assignee: nadeem.vawda messages: 152006 nosy: nadeem.vawda priority: normal severity: normal stage: needs patch status: open title: SIGBUS i

[issue5804] Add an 'offset' argument to zlib.decompress

Changes by Nadeem Vawda : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5784] raw deflate format and zlib module

Changes by Nadeem Vawda : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue8536] Support new features of ZLIB 1.2.4

Changes by Nadeem Vawda : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue5210] zlib does not indicate end of compressed stream properly

Changes by Nadeem Vawda : -- nosy: +nadeem.vawda ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyt

[issue13872] socket.detach doesn't mark socket._closed

New submission from Matt Joiner : socket.socket.detach doesn't mark the socket._closed flag. The flag is specific to the Python wrapper, so the fix is put there. Test included. -- components: Library (Lib) files: socket-detach-mark-closed.patch keywords: patch messages: 152005 nosy: ana

[issue11457] os.stat(): add new fields to get timestamps as Decimal objects with nanosecond resolution

Larry Hastings added the comment: Victor: I *think* Raymond's comments were directed at my patch, not yours. -- ___ Python tracker ___ __

[issue11457] os.stat(): add new fields to get timestamps as Decimal objects with nanosecond resolution

STINNER Victor added the comment: > Have you researched how other languages plan to expose sub-millisecond times? >  The isn't an API that will get points for originality.  Also, it needs to be > an API that is time efficient (many scripts use os.stat() frequently to scan > files for changes

[issue13455] Reorganize tracker docs in the devguide

Changes by Ezio Melotti : -- stage: needs patch -> patch review type: -> enhancement ___ Python tracker ___ ___ Python-bugs-list mail

[issue13435] Copybutton does not hide tracebacks

Ezio Melotti added the comment: This should be fixed now. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue13863] import.c sometimes generates incorrect timestamps on Windows + NTFS

Mark Dickinson added the comment: Also seen on Windows Vista; seems to be a general Windows + NTFS problem. Changing title to make it clearer that this is a core language issue. It seems as though the correct fix would be to use something like GetFileInformationByHandle in place of the fstat

[issue13870] Out-of-date comment in collections/__init__.py ordered dict

Changes by Raymond Hettinger : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue13870] Out-of-date comment in collections/__init__.py ordered dict

Roundup Robot added the comment: New changeset f7283825effa by Raymond Hettinger in branch '3.2': Issue 13870: Fix out of date comment. http://hg.python.org/cpython/rev/f7283825effa -- nosy: +python-dev ___ Python tracker