[issue5739] Language reference is ambiguous regarding next() method lookup

Terry J. Reedy added the comment: I was surprised when this came up with another issue. Why does CPython behave that way? Accident or justified decision? -- nosy: +tjreedy ___ Python tracker _

[issue5779] _elementtree import can fail silently

Changes by Benjamin Peterson : -- resolution: -> duplicate ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue5783] IDLE cannot find windows chm file

Martin v. Löwis added the comment: > Just checked Python2.5.4 and its CHM file is Python25.chm. So > everything is fine with that release. True. The renaming happened with the switch to sphinx. -- ___ Python tracker

[issue5783] IDLE cannot find windows chm file

Martin v. Löwis added the comment: > The release process needs to have a step that validates that the CHM > file works from IDLE. I personally can't perform such testing steps, perhaps unless somebody maintains a list of such steps for me. Instead, I think such problems must be detected during

[issue5764] 2.6.2 Python Manuals CHM file seems broken

Martin v. Löwis added the comment: > Are you also going to update the original MSI file so that people get a > correct installation straight-away? No. -- ___ Python tracker ___

[issue5783] IDLE cannot find windows chm file

Martin v. Löwis added the comment: > What changed here? We switched to sphinx, and the makefiles put the full version into the output files. > ISTM that IDLE was always looking for the same name > and that the new part is that the build procedure has been been changed > (the step where the "ma

[issue3102] ctypes defines global symbols

Martin v. Löwis added the comment: Looks fine to me, except that I wouldn't call things "My*" (but I do understand that this unrelated to this issue). -- ___ Python tracker ___ _

[issue5783] IDLE cannot find windows chm file

Raymond Hettinger added the comment: Just checked Python2.5.4 and its CHM file is Python25.chm. So everything is fine with that release. -- ___ Python tracker ___ __

[issue5783] IDLE cannot find windows chm file

Raymond Hettinger added the comment: It looks like IDLE has been the same since 2004: http://svn.python.org/view/python/trunk/Lib/idlelib/EditorWindow.py?view=diff&r1=36600&r2=36601 The "correct" filename is what has changed. The release process needs to have a step that validates that the

[issue5778] sys.version format differs between MSC and GCC

Changes by Martin v. Löwis : -- assignee: loewis -> ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue5778] sys.version format differs between MSC and GCC

Changes by Martin v. Löwis : -- priority: -> low ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue5778] sys.version format differs between MSC and GCC

Changes by Martin v. Löwis : -- type: -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue5780] test_float fails for 'legacy' float repr style

Mark Dickinson added the comment: Committed, with the fixups Eric pointed out, in r71692. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue5784] raw deflate format and zlib module

paul rubin added the comment: I should have mentioned, the docs do say "When wbits is negative, the standard gzip header is suppressed; this is an undocumented feature of the zlib library, used for compatibility with unzip‘s compression file format" but this wasn't enough at the time to figure o

[issue5784] raw deflate format and zlib module

Changes by paul rubin : -- components: +Library (Lib) type: -> feature request versions: +Python 2.5 ___ Python tracker ___ ___ Python

[issue5784] raw deflate format and zlib module

New submission from paul rubin : The zlib module doesn't support raw deflate format, so it doesn't completely interoperate with php's "gzdeflate" function and fails to decompress some strings that web browsers can decompress. A workaround is to use a special zlib feature and pass the value -15 a

[issue1869] Builtin round function is sometimes inaccurate for floats

Changes by Mark Dickinson : -- components: +Interpreter Core ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue1869] Builtin round function is sometimes inaccurate for floats

Mark Dickinson added the comment: Updated patch, with tests. -- stage: test needed -> patch review Added file: http://bugs.python.org/file13715/issue1869_2.patch ___ Python tracker _

[issue5773] Crash on shutdown after os.fdopen(2) in debug builds

Antoine Pitrou added the comment: I thought there was a _PyVerify_Fd() just for that, why couldn't it be used here too? (not that I think sparkling _PyVerify_Fd() everywhere in our code base is reasonable and maintainable, but I didn't make that choice :-)) -- nosy: +pitrou ___

[issue5734] Fix BufferedRWPair

Antoine Pitrou added the comment: Reviewers: report_bugs.python.org, Message: Here are some comments. In general, I think the changes to _pyio.py are unwarranted (even though I dislike the naming of _checkReadable and _checkWritable). http://codereview.appspot.com/40126/diff/1/2 File Lib/_pyio

[issue5734] BufferedRWPair broken

Antoine Pitrou added the comment: I've uploaded the patch for code review here: http://codereview.appspot.com/40126 -- ___ Python tracker ___

[issue1869] Builtin round function is sometimes inaccurate for floats

Mark Dickinson added the comment: Note that the correctly rounded string<->decimal code only exists in 3.1, so it won't be possible to backport all this good stuff to 2.7. -- ___ Python tracker

[issue1869] Builtin round function is sometimes inaccurate for floats

Mark Dickinson added the comment: Here's a patch that improves float rounding in a number of respects: (1) (when available) it uses the recently added correctly-rounded str <- > float conversions in Python/dtoa.c. This means that: - round(x, n) finally does what the docs say it does: rounds

[issue5764] 2.6.2 Python Manuals CHM file seems broken

Raymond Hettinger added the comment: Are you also going to update the original MSI file so that people get a correct installation straight-away? -- nosy: +rhettinger ___ Python tracker _

[issue5783] IDLE cannot find windows chm file

Raymond Hettinger added the comment: What changed here? ISTM that IDLE was always looking for the same name and that the new part is that the build procedure has been been changed (the step where the "make htmlhelp" output file is moved to ./Doc and renamed). -- __

[issue5764] 2.6.2 Python Manuals CHM file seems broken

Martin v. Löwis added the comment: On http://www.python.org/download/releases/2.6.2/ we now provide a fixed version of the CHM file. -- nosy: +loewis ___ Python tracker ___ ___

[issue5783] IDLE cannot find windows chm file

Martin v. Löwis added the comment: It's actually vice versa - IDLE should open the file under its correct name. -- nosy: +loewis ___ Python tracker ___ __

[issue5783] IDLE cannot find windows chm file

Raymond Hettinger added the comment: This also applies to Python31a2.chm --> Python31.chm -- versions: +Python 3.1 ___ Python tracker ___

[issue5783] IDLE cannot find windows chm file

New submission from Raymond Hettinger : The Doc/Python262.chm file needs to be named Doc/Python26.chm so that IDLE can find it. The current release cannot find the chm file at all so it falls back to the on-line docs at http://www.python.org/doc/current . -- assignee: benjamin.peterson

[issue5782] ',' formatting with empty format type '' (PEP 378)

Eric Smith added the comment: I updated the PEP in r71686. I'll fix the code and add a test after I backport the entire thing to 2.7. -- ___ Python tracker ___ __

[issue5782] ',' formatting with empty format type '' (PEP 378)

Mark Dickinson added the comment: Sounds good to me, too. It looks as though the Decimal type already does this: Python 3.1a2+ (py3k:71669:71684M, Apr 17 2009, 19:23:53) [GCC 4.0.1 (Apple Inc. build 5490)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> fr

[issue5782] ',' formatting with empty format type '' (PEP 378)

Raymond Hettinger added the comment: I concur. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue3102] ctypes defines global symbols

Thomas Heller added the comment: Here is a quite large patch (300 lines) against svn trunk that renames a lot of symbols. The list of symbols, listed by 'nm -g --defined-only _ctypes.so' is as follows: thel...@tubu32:~/devel/trunk$ find . -name _ctypes.so | xargs nm -g --defined-only 00011d07 T

[issue3754] minimal cross-compilation support for configure

Changes by Victor Godoy Poluceno : -- nosy: +victorpoluceno ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue4482] 10e667.__format__('+') should return 'inf'

Daniel Stutzbach added the comment: I used 'inf' instead of "+inf' because the original bug report states that the docs say it should be 'inf'. Now that I actually look at the docs, I don't agree with the original report's interpretation and agree that '+inf' is better. -- ___

[issue708320] DistributionMetaData error ?

Vah Rashim added the comment: I'm running py2exe on python 2.6 and have this error, too. I'm look through distutils/dist.py and read following: self.metadata = DistributionMetadata() method_basenames = dir(self.metadata) + \ ['fullname', 'contact', 'contact_email'] for bas

[issue5782] ',' formatting with empty format type '' (PEP 378)

New submission from Eric Smith : PEP 378 says that the ',' format option applies to types 'd', 'e', 'f', 'g', 'E', 'G', '%' and 'F'. I think this should also be extended to include the empty type ''. This only makes a difference for floats. For ints, '' is the same as 'd', but for floats '' is d

[issue5780] test_float fails for 'legacy' float repr style

Eric Smith added the comment: I definitely think that if you go with isdigit, you need the macro. I've been bitten by this in 3.0. My actual suggestion is to go with isdigit and the macro everywhere in this file and all files. But for just this checkin, ISDIGIT is probably best. -- _

[issue5781] Legacy float repr is used unnecessarily on some platforms

New submission from Mark Dickinson : The current defines in pyport.h mean that we don't use Gay's code for short float repr if there's evidence of double rounding. However, there's one situation where double rounding occurs and we can still use Gay's code: namely, when the configure script has

[issue5780] test_float fails for 'legacy' float repr style

Mark Dickinson added the comment: I seem to recall that despite the C standards, there are platforms around where isdigit and isxdigit are still locale aware. This bit me when I implemented float.fromhex: see r65964. And my man page for isdigit says: COMPATIBILITY The 4.4BSD extension

[issue5780] test_float fails for 'legacy' float repr style

Eric Smith added the comment: Also, remove_trailing_zeros should go inside the #ifdef so it's not included if Gay's code is being used. -- ___ Python tracker ___

[issue5780] test_float fails for 'legacy' float repr style

Eric Smith added the comment: I agree that there should be 2 behaviors, not 3. This patch looks okay to me, and tests pass both with and without defining PY_NO_SHORT_FLOAT_REPR. One nit: You don't need to use Py_CHARMASK when using the ISDIGIT macro locally defined in pystrtod.c. On the other

[issue1580] Use shorter float repr when possible

Mark Dickinson added the comment: Closing this. There are a few known problems remaining, but they've all got their own issue numbers: see issue 5780, issue 4482. -- resolution: -> accepted stage: -> committed/rejected status: open -> closed ___

[issue5780] test_float fails for 'legacy' float repr style

Mark Dickinson added the comment: On second thoughts, I think that repr shouldn't change: 'legacy' repr format should mean that it *is* exactly the same as before, including the switch at 1e17 instead of 1e16. Otherwise there will be 3 possibilities for repr output: 'short' repr, 'legacy' rep

[issue5780] test_float fails for 'legacy' float repr style

Changes by Mark Dickinson : Removed file: http://bugs.python.org/file13711/issue5780.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue5780] test_float fails for 'legacy' float repr style

Mark Dickinson added the comment: Here's a patch. Eric, do you have time to check this over for general sanity? -- keywords: +patch Added file: http://bugs.python.org/file13711/issue5780.patch ___ Python tracker

[issue5780] test_float fails for 'legacy' float repr style

New submission from Mark Dickinson : After: CC="gcc -DPY_NO_SHORT_FLOAT_REPR" ./configure && make test_format_testfile in test_float fails with: test.support.TestFailed: Traceback (most recent call last): File "Lib/test/test_float.py", line 341, in test_format_testfile self.assertEqual(

[issue5779] _elementtree import can fail silently

Matteo Bertini added the comment: Ups, I duplicated myself... issue3475 -- status: open -> closed ___ Python tracker ___ ___ Python-bu

[issue4305] ctypes fails to build on mipsel-linux-gnu (detects mips instead of mipsel)

Thomas Heller added the comment: Joshua Kinard schrieb: > Joshua Kinard added the comment: > > Is there any movement on this perchance? Just bumped into this on my > MIPS platform and discovered this bug. There is no MIPS buildbot at the moment, and I'm unclear which one of the patches solve

[issue5779] _elementtree import can fail silently

New submission from Matteo Bertini : (the patch is old, I forwarded it to Fredrik but I forgot to open the bug) Playing with PyInstaller I have found that the final part of _elementtree.c: Index: Modules/_elementtree.c === --- Modu

[issue2531] float compared to decimal is silently incorrect.

Mark Dickinson added the comment: The downside is the potential confusion arising from using one method (comparison of actual numerical value) for <, <=, >, >=, and a different method (decimals and floats are never equal) for == and !=. -- ___ Python

[issue5778] sys.version format differs between MSC and GCC

Changes by Georg Brandl : -- assignee: -> loewis nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5778] sys.version format differs between MSC and GCC

New submission from Toshihiro Kamiya : The value of sys.version includes a new-line char in GCC build. '2.5.2 (r252:60911, Oct 5 2008, 19:24:49) \n[GCC 4.3.2]' MSC build doesn't. '2.6.2 (r262:71605, Apr 14 2009, 22:46:50) [MSC v.1500 64 bit (AMD64)]' This seems a kind of pitfall for the develo

[issue2531] float compared to decimal is silently incorrect.

Raymond Hettinger added the comment: I'm not seeing the downside. This gives better answers than it does now but doesn't commit us to anything else. -- ___ Python tracker ___ __

[issue2531] float compared to decimal is silently incorrect.

Mark Dickinson added the comment: On Fri, Apr 17, 2009 at 3:45 AM, Raymond Hettinger wrote: > Mark, any thoughts?  I would like to apply this patch for ordering > comparisons other than __eq__ and __ne__. Hi Raymond, Sorry for not responding to this sooner. I'll post something to the issue tr

[issue5777] unable to search in python V3 documentation

New submission from Andreas Otto : Hi, if I search for "sys.argv" I get Your search did not match any documents. Please make sure that all words are spelled correctly and that you've selected enough categories. but its available at: http://docs.python.org/3.0/library/sys.html -- as

[issue5776] RPM build error with python-2.6.spec

New submission from Yasushi Iwata : I found some typo and mistakes in python-2.6.spec. -- components: Demos and Tools files: python-2.6.spec.patch keywords: patch messages: 86056 nosy: yasusii severity: normal status: open title: RPM build error with python-2.6.spec versions: Python 2.6