[issue11896] Save on Close fails in IDLE, from Linux system

Ned Deily added the comment: Thanks for the precise test case. I am able to reproduce the failure on OS X using the MacPorts X11-Tk Tkinter but not with the standard OS X AquaTk Tkinter. -- assignee: -> ned.deily nosy: +ned.deily stage: -> needs patch __

[issue11888] Add C99's log2() function to the math library

Mark Dickinson added the comment: See also issue 3724. I'm -0 on this: between log(x, 2) and int.bit_length, there's not much need for log2. log(x, 2) should be plenty accurate enough for most numerical needs; the exception is when you're taking log base 2 of an integer and need a guarant

[issue11888] Add C99's log2() function to the math library

STINNER Victor added the comment: > The main issue is that we'd have to provide (and maintain) our own > implementation of log2 for Windows (and other OSs that don't have all > the C99 support. Solaris?) No, we don't have to. Python has already a lot of optional functions, see for example the

[issue10596] modulo operator bug

Mark Dickinson added the comment: Raymond: just curious---why do you ask? Did this fix break something? -- ___ Python tracker ___ __

[issue11888] Add C99's log2() function to the math library

Mark Dickinson added the comment: > We can provide log2() only if the C library has this function. Big -1 from me: I'd hate to see working Python scripts written on Unix fail on Windows because of a missing log2. -- ___ Python tracker

[issue11888] Add C99's log2() function to the math library

Mark Dickinson added the comment: Rather than reinventing the wheel, it may be worth looking at what numpy does here. -- ___ Python tracker ___

[issue11888] Add C99's log2() function to the math library

Mark Dickinson added the comment: > it may be worth looking at what numpy does here. ... or it may not. NumPy just uses (approximation to 1/log(2)) * log(x) when log2 doesn't already exist. And indeed, on Windows: Python 2.7.1 |EPD 7.0-2 (64-bit)| (r271:86832, Dec 2 2010, 10:23:25) [MSC v

[issue11895] pybench prep_times calculation error

Marc-Andre Lemburg added the comment: Mikhail Terekhov wrote: > > New submission from Mikhail Terekhov : > > For some time now my builds of python 3.2 on x86_64 platform in SuSE OBS are > failing depending on the phase of the moon. The spec file for the > python3-base package uses 'make prof

[issue11892] Compiler warning: warning: implicit declaration of function 'finite'

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

[issue10042] total_ordering

Francesco Ricciardi added the comment: On the one hand, it's not just a matter of total_ordering and rich comparison operators, because all user defined operators may return NotImplemented when they get types that they don't know how to handle. On the other hand, if such a decision is taken,

[issue11897] [PATCH] Documentation: fix typo, absolute_import not absolute_imports

New submission from intgr : The "Porting Python 2 Code to Python 3" guide currently says: from __future__ import absolute_imports However it should be singular: from __future__ import absolute_import -- assignee: docs@python components: Documentation files: absolute_import_singula

[issue11897] [PATCH] Documentation: fix typo, absolute_import not absolute_imports

Roundup Robot added the comment: New changeset 05a7d3048c49 by Ezio Melotti in branch '3.2': #11897: Fix typo in porting howto. Patch by Marti Raudsepp. http://hg.python.org/cpython/rev/05a7d3048c49 New changeset 968fba3f34b3 by Ezio Melotti in branch 'default': #11897: Merge with 3.2. http://h

[issue11897] [PATCH] Documentation: fix typo, absolute_import not absolute_imports

Ezio Melotti added the comment: Fixed, thanks for the patch! -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker

[issue11885] argparse docs needs fixing

Roundup Robot added the comment: New changeset 0f084f150198 by Ezio Melotti in branch '2.7': #11885: capitalize Python. http://hg.python.org/cpython/rev/0f084f150198 New changeset fb6affc7b973 by Ezio Melotti in branch '3.2': #11885: capitalize Python. http://hg.python.org/cpython/rev/fb6affc7b

[issue11885] argparse docs needs fixing

Ezio Melotti added the comment: Fixed, thanks for the report. -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue11885] argparse docs needs fixing

Changes by Ezio Melotti : -- assignee: docs@python -> ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue11898] Sending binary data with a POST request in httplib can cause Unicode exceptions

New submission from Bernhard Rosenkraenzer : Sending e.g. a JPEG file with a httplib POST request (e.g. through mechanize) can result in an error like this: File "/usr/lib64/python2.7/httplib.py", line 947, in request self._send_request(method, url, body, headers) File "/usr/lib64/pytho

[issue11898] Sending binary data with a POST request in httplib can cause Unicode exceptions

Changes by Ezio Melotti : -- nosy: +ezio.melotti, orsenthil ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: I think PEP 3115 is OK - the error about all metaclasses inheriting from type was a mistake on my part (I thought the ability to create non-type metaclasses went away along with old-style classes, but I was simply wrong on that point). That got me curious as to

[issue11877] Change os.fsync() to support physical backing store syncs

Steffen Daode Nurpmeso added the comment: I'm convinced. And i've rewritten the patch. Now fsync(2) is always called first *regardless* of the new optional argument. The documentation is (a little bit) better now. And i've added support for NetBSD, AIX and Linux; though: - for AIX i'm testin

[issue11877] Change os.fsync() to support physical backing store syncs

Changes by Steffen Daode Nurpmeso : Removed file: http://bugs.python.org/file21718/fsync.diff ___ Python tracker ___ ___ Python-bugs-list mail

[issue11877] Change os.fsync() to support physical backing store syncs

Steffen Daode Nurpmeso added the comment: P.S.: dito Linux and NetBSD. I've reused preprocessor tests we've discovered internally over the past years, but i cannot test this here. I could test Linux next Tuesday, though. -- ___ Pyt

[issue11877] Change os.fsync() to support physical backing store syncs

STINNER Victor added the comment: 11877.2.diff: On Mac OS X, fsync(fd, full_sync=True); fsync(fd) do a full sync twice. You should restore the old file flags at fsync() exit. Or this surprising behaviour should be documented. -- ___ Python tracker

[issue11885] argparse docs needs fixing

Éric Araujo added the comment: >> "When most in optparse had either been copy-pasted over or monkey-patched >> ..." > Word "everything" was removed. The result is grammatically incorrect :) I’d suggest “most of argparse”. > comma was deleted after "that is". Both versions were grammatically c

[issue11885] argparse docs needs fixing

Éric Araujo added the comment: most of optparse* -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue11584] email.decode_header fails if msg.__getitem__ returns Header object

R. David Murray added the comment: My fix (and the tests) for this are wrong. decode_header returns (binary, charset) pairs, but the chunks list is (string, charset) pairs. -- stage: committed/rejected -> needs patch status: closed -> open ___ Pyth

[issue1322] platform.dist() has unpredictable result under Linux

Éric Araujo added the comment: [Zooko] > I just read back through this ticket, but I didn't understand exactly > what MAL wanted to have different from what this Python function > currently does: It may be this: > It's better to follow the approach taken by lsb_release and then > add calling l

[issue11899] TarFile.gettarinfo modifies self.inodes

New submission from Michael Gold : When I call tar.gettarinfo (where tar is a TarFile instance), the inode information is inserted into tar.inodes. If I later call tar.gettarinfo on a linked file, the returned TarInfo will have type LNKTYPE. I think it's incorrect to store this information in

[issue11877] Change os.fsync() to support physical backing store syncs

Steffen Daode Nurpmeso added the comment: Ok, 11877.3.diff uses either-or. -- Added file: http://bugs.python.org/file21749/11877.3.diff ___ Python tracker ___diff --git a/Doc/li

[issue11877] Change os.fsync() to support physical backing store syncs

Changes by Steffen Daode Nurpmeso : Removed file: http://bugs.python.org/file21742/11877.optarg-1.diff ___ Python tracker ___ ___ Python-bugs-

[issue11877] Change os.fsync() to support physical backing store syncs

Changes by Steffen Daode Nurpmeso : Removed file: http://bugs.python.org/file21748/11877.2.diff ___ Python tracker ___ ___ Python-bugs-list ma

[issue9742] Python 2.7: math module fails to build on Solaris 9

David Schnur added the comment: I encountered this problem when updating from 2.6.4 to 2.7.1 on Solaris 8, which also doesn't have 'round'. I tried srmadsen's --whole-archive option, but it wasn't recognized by the (somewhat ancient) tools on that machine. I solved the problem by just editin

[issue11777] Executor.map does not submit futures until iter.next() is called

Éric Araujo added the comment: Just a bystander remark: when you use present in the commit message and Misc/NEWS entry (like in “Executor.map does not submit futures until iter.next() is called”), I don’t know whether it is the behavior being fixed (“X used to do Y”) or the new, correct behav

[issue11899] TarFile.gettarinfo modifies self.inodes

Michael Gold added the comment: Actually, TarFile should also have a separate method to take a TarInfo instance and modify its type to LNKTYPE if applicable. gettarinfo can call that. This way the user can use a TarInfo object created before any files are added, and can easily get this linki

[issue1294232] Error in metaclass search order

Guido van Rossum added the comment: Thanks for diving deep! How much of this can we claim as a bug and how much as a feature? -- ___ Python tracker ___ __

[issue10932] distutils.core.setup - data_files misbehaviour ?

Éric Araujo added the comment: Patch looks good. Detail: I’d find a call to basename more readable than i.split('/')[-1:][0]. Does this need a test in test_manifest too? A doc update? -- ___ Python tracker ___

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: As near as I can tell, the only visible behavioural change with Daniel's patch (updated as per my last comment) will be that the two error cases noted above (i.e. when an explicit metaclass or the first parent type's metaclass is not the most derived metaclass)

[issue1294232] Error in metaclass search order

Nick Coghlan added the comment: Commenting on the latest patch here, since the Rietveld integration isn't coping with the "hg extdiff" output (I would guess that the revision numbers in the pathnames are confusing the script that attempts to determine the base revision). Aside from the note

[issue6191] HTMLParser attribute parsing - 2 test cases when it fails

Paweł Widera added the comment: No. As the value of the href attribute is not suppose to contain spaces, I'd rather expect the parser to assume that there is an ending " missing before the space. -- ___ Python tracker

[issue11877] Change os.fsync() to support physical backing store syncs

Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue11898] Sending binary data with a POST request in httplib can cause Unicode exceptions

Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue11382] some posix module functions unnecessarily release the GIL

Charles-Francois Natali added the comment: Is there anything I can do to help this move forward ? -- ___ Python tracker ___ ___ Pytho

[issue11900] 2.7.1 unicode subclasses not calling __str__() for print statement

New submission from Dave Opstad : Python 2.7.1 doesn't appear to do the usual implicit call to str() for subclasses of unicode. In the following snippet, I would have expected print myTest and print str(myTest) to behave the same: >>> class Test(unicode): ... def __str__(self): ... print

[issue11901] Docs for sys.hexversion should give the algorithm

New submission from R. David Murray : I went to write a test that would trigger something if it was run on 3.3.0, and had to look in the source code to figure out what the hexversion for that would be. I think the hexversion algorithm should be documented in its sys entry. -- assignee

[issue11900] 2.7.1 unicode subclasses not calling __str__() for print statement

R. David Murray added the comment: You subclassed unicode. So print printed the value of your unicode object, which didn't need coercion. -- nosy: +r.david.murray resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Pyth

[issue11885] argparse docs needs fixing

Boštjan Mejak added the comment: Eric, you are great! Thanks for fixing the docs. ;) -- Added file: http://bugs.python.org/file21750/unnamed ___ Python tracker ___Eric, you are

[issue11900] 2.7.1 unicode subclasses not calling __str__() for print statement

R. David Murray added the comment: For the record, this isn't as simple as I made it sound. See, for example, issue 9196. -- ___ Python tracker ___ ___

[issue11877] Change os.fsync() to support physical backing store syncs

Charles-Francois Natali added the comment: I'm -10 on sync_file_range on Linux: - it doesn't update the file metadata, so there's a high chance of corruption after a crash - last time I checked, it didn't flush the disk cache (well, it probably does if barriers are enabled, but that's also the

[issue11902] typo in argparse doc's: "action.."

New submission from Vladimir Rutsky : There is a typo in argparse module documentation: "The ``nargs`` keyword argument associates a different number of command-line arguments with a single action.." (two dots at end). Patch based on official http://svn.python.org/projects/python/branches/py3k/

[issue11900] 2.7.1 unicode subclasses not calling __str__() for print statement

Dave Opstad added the comment: I guess I was confused by the inconsistency with Python 3, which *does* call the __str__ method, even though, again, no coercion is needed: Python 3.2 (r32:88452, Feb 20 2011, 10:19:59) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type "help", "copyright", "cre

[issue11903] Incorrect test code in test_logging.py

New submission from Stefan Behnel : In test file test_logging.py, around line 2359, list.append() is called with two arguments instead of one. I suppose it is meant to be called with a tuple. class ModuleLevelMiscTest(BaseTest): [...] def _test_log(self, method, level=None): cal

[issue11904] incorrect reStructuredText formatting in argparse module

New submission from Vladimir Rutsky : In Python 2.7 and 3 branch at http://svn.python.org/projects/python/branches/py3k/ file Doc/library/argparse.rst has incorrectly formatted list at line 648: > * ``'store'`` - This just stores the argument's value. This is the default >action. For exam

[issue11905] typo in argparse doc's: missing dot at end of sentence

New submission from Vladimir Rutsky : There is missed dot at end of sentence in argparse module documentation. Please see attached patch for details. Patch based on official http://svn.python.org/projects/python/branches/py3k/ repository, but typo is also noted in Python 2.7 documentation. --

[issue11902] typo in argparse doc's: "action.."

Roundup Robot added the comment: New changeset e8464256b4d7 by Ezio Melotti in branch '2.7': #11902: Fix typo in argparse doc. Noticed by Vladimir Rutsky. http://hg.python.org/cpython/rev/e8464256b4d7 New changeset 88df1ef4eec8 by Ezio Melotti in branch '3.2': #11902: Fix typo in argparse doc.

[issue11903] Incorrect test code in test_logging.py

Santoso Wijaya added the comment: Introduced in changeset c7f7672b70a9. -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-lis

[issue11902] typo in argparse doc's: "action.."

Ezio Melotti added the comment: Fixed, thanks for the report. BTW we are using HG now (http://hg.python.org/cpython) and patches should be submitted against the oldest applicable branch (either 2.7 or 3.2 is fine in this case). More info at http://docs.python.org/devguide/. -- assign

[issue11584] email.decode_header fails if msg.__getitem__ returns Header object

R. David Murray added the comment: Note that when this is fixed, make_header on the return value from decode_header will fail because it doesn't know now to handle unknown-8bit. -- ___ Python tracker

[issue11903] Incorrect test code in test_logging.py

Santoso Wijaya added the comment: Simple fix. -- keywords: +patch Added file: http://bugs.python.org/file21753/issue11903_py33.patch ___ Python tracker ___ _

[issue11904] incorrect reStructuredText formatting in argparse module

Roundup Robot added the comment: New changeset 79f3ae389dae by Ezio Melotti in branch '2.7': #11904: fix indentation in argparse doc. Noticed by Vladimir Rutsky. http://hg.python.org/cpython/rev/79f3ae389dae New changeset 473fada5f1b7 by Ezio Melotti in branch '3.2': #11904: fix indentation in

[issue11905] typo in argparse doc's: missing dot at end of sentence

Roundup Robot added the comment: New changeset f6ea7abc4eb2 by Ezio Melotti in branch '2.7': #11905: fix missing full stop in argparse doc. Noticed by Vladimir Rutsky. http://hg.python.org/cpython/rev/f6ea7abc4eb2 New changeset 15f482996880 by Ezio Melotti in branch '3.2': #11905: fix missing f

[issue11905] typo in argparse doc's: missing dot at end of sentence

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 3.2, Python 3.3 -Python 3.4 ___ Py

[issue11904] incorrect reStructuredText formatting in argparse module

Ezio Melotti added the comment: Fixed, thanks for the report! -- assignee: docs@python -> ezio.melotti nosy: +ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 3.2, Python 3.3 -Python 3.4 ___ Py

[issue11900] 2.7.1 unicode subclasses not calling __str__() for print statement

R. David Murray added the comment: Well, it's possible I'm wrong and you've found a bug. There are numerous differences between 2 and 3 in both string handling and special method handling, though, so it may be hard to pin down. If you poke around a bit more and still think it is a bug, plea

[issue11877] Change os.fsync() to support physical backing store syncs

Steffen Daode Nurpmeso added the comment: Charles-Francois Natali wrote: > I'm -10 on sync_file_range on Linux: > [...] last time I checked [...] I just looked at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=fs/sync.c;h=c38ec163da6ccba00a0146c75606c1b548b31343;

[issue11877] Change os.fsync() to support physical backing store syncs

Charles-Francois Natali added the comment: > and it seems - as far as i understand what i read - that you're > still right; and, furthermore, that fsync() does everything > anyway.  (But here an idiot is talking about *very* complicated > stuff.) > I just double-checked, and indeed, fsync does

[issue1294232] Error in metaclass search order

Daniel Urban added the comment: I'm attaching the updated patch. Changes: - Special casing objects we can't do the metaclass computation for. - Tests for these. - Adding tests for the order of __new__ calls. The special case isn't just checking if the object is a class, but instead checking i

[issue1322] platform.dist() has unpredictable result under Linux

Marc-Andre Lemburg added the comment: Éric Araujo wrote: > > Éric Araujo added the comment: > > [Zooko] >> I just read back through this ticket, but I didn't understand exactly >> what MAL wanted to have different from what this Python function >> currently does: > > It may be this: > >> It

[issue1294232] Error in metaclass search order

Daniel Urban added the comment: I've just realized, that my patch still breaks a case, that previously worked: when the bases are not classes. This works in 3.2, but not with my patch: >>> class Foo: # not a subclass of type! ... def __new__(mcls, name='foo', bases=(), namespace={}): ...

[issue11903] Incorrect test code in test_logging.py

Vinay Sajip added the comment: Checked in, see changeset fecf9e6d7630 - thanks. -- assignee: -> vinay.sajip nosy: +vinay.sajip resolution: -> fixed status: open -> closed ___ Python tracker _

[issue9196] Improve docs for string interpolation "%s" re Unicode strings

Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue11846] Remove non-guaranteed implementation details from docs.

Anthony Long added the comment: I'll have a doc patch shortly. Also, I am working on defining a solid range. Memory is not an issue like it was back in 1991 when this range was originally implemented, so we can go higher and get a bigger performance boost. This will be very important (to som

[issue11906] Test_argparse failure but only in interactive mode

New submission from Terry J. Reedy : (3.1 not checked because it seems not to have test_argparse) Python 2.7 or 3.2, WinXP these pass: C:\Programs\Python27>python -m test.regrtest test_argparse C:\Programs\Python32>python -m test test_argparse [1/1] test_argparse 1 test OK. C:\Programs\Python32>

[issue9228] Make changes in the PATH and PATHEXT on installation

Nick Coghlan added the comment: That's not correct - we've merely pointed out that it isn't as easy as most people seem to think. For the POSIX world, there is a version management scheme based on symlinks in /usr/bin (or /usr/local/bin) and it is easy to add and remove entries independently

[issue11846] Remove non-guaranteed implementation details from docs.

Raymond Hettinger added the comment: > Memory is not an issue like it was back in 1991 when > this range was originally implemented, so we can go > higher and get a bigger performance boost. Please don't do this. Memory is still important to a lot of people. Also, there is *very* little pa

[issue11846] Remove non-guaranteed implementation details from docs.

Anthony Long added the comment: My plan is to document it, as it exists, in the current implementation. That's a start atleast, and will provide an entry point for further documentation in the future should it be changed again. -- ___ Python tracke

[issue1294232] Error in metaclass search order

Daniel Urban added the comment: Okay, probably the check in my previous patch was too strict (sorry for the noise). I'm attaching an updated patch again. Now the algorithm in __build_class__ is this: 1. If an object is explicitly given with the metaclass keyword, that is the "starting meta

[issue1294232] Error in metaclass search order

Changes by Daniel Urban : Removed file: http://bugs.python.org/file21755/issue11256_4.patch ___ Python tracker ___ ___ Python-bugs-list mail

[issue1294232] Error in metaclass search order

Changes by Daniel Urban : Added file: http://bugs.python.org/file21756/issue_1294232_4.patch ___ Python tracker ___ ___ Python-bugs-list mai