[issue644744] bdist_rpm fails when installing man pages

Changes by Joe Julian : -- nosy: +jjulian ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ned Deily added the comment: Martin, just to be clear: the purpose of the new feature *is* to allow the choice between 32-bit/64-bit and that is important. My comment was that the downside of the submitted fix, as it stands, would be to not allow choosing archs only for pythons built with th

[issue5127] Use Py_UCS4 instead of Py_UNICODE in unicodectype.c

Amaury Forgeot d'Arc added the comment: > I don't see the point in changing the various conversion APIs in the > unicode database to return Py_UCS4 when there are no conversions that > map code points between BMP and non-BMP. For consistency: if Py_UNICODE_ISPRINTABLE is changed to take Py_UCS4

[issue7617] distutils.unixccompiler.UnixCCompiler.runtime_library_dir_option() should recognize ${configuration_name}-gcc

Tarek Ziadé added the comment: done in r77377, r77378, r77380, r77381 Thanks! -- status: open -> closed ___ Python tracker ___ ___ Py

[issue5640] Wrong print() result when unicode error handler is not 'strict'

Changes by Ezio Melotti : -- versions: +Python 3.2 -Python 3.0 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue7071] distutils and IronPython compatibility

Tarek Ziadé added the comment: merged in 2.6 in r77376 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue7661] compiling ctypes fails with non-ascii path

New submission from Antoine Pitrou : Traceback (most recent call last): File "./setup.py", line 1933, in main() File "./setup.py", line 1928, in main 'Lib/smtpd.py'] File "/home/buildbot/cpython-ucs4-nonascii-€/trunk.pitrou-ubuntu-wide/build/Lib/distutils/core.py", line 152, in

[issue7632] dtoa.c: oversize b in quorem

Mark Dickinson added the comment: Okay, I think I've found the cause of the second rounding bug above: at the end of the bigcomp function there's a correction block that looks like ... else if (dd < 0) { if (!dsign) /* does not happen for round-near */ retlow1:

[issue706263] print raises exception when no console available

Alan Justino added the comment: FWIW: I don't know if it changes anything, but when deploying Django projects on some clients who uses Windows as server, I'm using this piece of code to workarround this issue: ## Fixes "IOError: [Errno 9] Bad file descriptor" when in pythonw.exe of Windows i

[issue5127] Use Py_UCS4 instead of Py_UNICODE in unicodectype.c

Marc-Andre Lemburg added the comment: I don't see the point in changing the various conversion APIs in the unicode database to return Py_UCS4 when there are no conversions that map code points between BMP and non-BMP. In order to solve the problem in question (unicode_repr() failing), we shou

[issue7643] What is an ASCII linebreak?

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > It's confusing. > > There's a specific annex UAX #14 which defines "Line Breaking Properties". > Some properties are defines as "Mandatory Line Breaks (non-tailorable)": > BK, CR, LF, NL

[issue7632] dtoa.c: oversize b in quorem

Mark Dickinson added the comment: Randomised testing quickly turned up another troublesome string for str -> float conversion: s = "94393431193180696942841837085033647913224148539854e-358" This one's actually giving incorrectly rounded results (the horror!) in a non-debug build of trunk, and

[issue7643] What is an ASCII linebreak?

Marc-Andre Lemburg added the comment: Florent Xicluna wrote: > > Florent Xicluna added the comment: > > Some technical background. > > == Unicode == > > According to the Unicode Standard Annex #9, a character with > bidirectional class B is a "Paragraph Separator". And “Because a > Paragrap

[issue7617] distutils.unixccompiler.UnixCCompiler.runtime_library_dir_option() should recognize ${configuration_name}-gcc

Changes by Tarek Ziadé : -- priority: -> normal resolution: -> accepted ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Martin v. Löwis added the comment: > As far as I can see, the only possible shortcoming of the patch is > that it restores the current behavior with a 2-way fat ppc/i386 build > with 10.4u (i.e. the way python.org installers are currently built); > that is, you would still not be able to use "ar

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file15793/issue7092_regrtest_clean.diff ___ Python tracker ___ ___ Python-bugs

[issue7316] Add a timeout functionality to common locking operations

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file15533/timedlock3.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7316] Add a timeout functionality to common locking operations

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file15352/timedlock2.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7316] Add a timeout functionality to common locking operations

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file15321/timedlock.patch ___ Python tracker ___ ___ Python-bugs-list mailing

[issue7316] Add a timeout functionality to common locking operations

Antoine Pitrou added the comment: Updated patch against newest py3k. -- Added file: http://bugs.python.org/file15795/timedlock4.patch ___ Python tracker ___ _

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Antoine Pitrou : Removed file: http://bugs.python.org/file15773/issue7092_cpickle.diff ___ Python tracker ___ ___ Python-bugs-list m

[issue7660] Two float('nan') are not equal

Mark Dickinson added the comment: >>> float('nan') == float('nan') False >>> float('nan') != float('nan') True This is deliberate, though perhaps surprising if you haven't seen it before. There's a long history of nan comparisons behaving this way (that is, x == nan always returns False, x !

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Antoine Pitrou added the comment: issue7092_cpickle.diff was committed to trunk and 2.6. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue7026] test_urllib: unsetting missing 'env' variable

Senthil Kumaran added the comment: Yes, I indeed, I quickly moved to patch it up in the trunk and did a svn submit -m "..." I had your big patch for tests in the trunk. I have reverted it for now and shall fix this one only. -- ___ Python tracker

[issue7660] Two float('nan') are not equal

New submission from Jean-Michel Fauth : I did not find any report about this. Windows 7, Python 2.6.4 >>> float('inf') == float('inf') True >>> float('-inf') == float('-inf') True >>> float('-inf') == float('inf') False >>> float('-inf') != float('inf') True >>> float('nan') == float('nan') Fal

[issue7659] Attribute assignment on object() instances raises wrong exception

R. David Murray added the comment: But an object to which you can assign attributes but which has no methods can be useful in a number of contexts. It's not a glorified dict, because attribute-style access is different from dict-style access. The main place I have used this (creating my own

[issue7659] Attribute assignment on object() instances raises wrong exception

Pascal Chambon added the comment: OK, eligible to QOTW:D -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue7026] test_urllib: unsetting missing 'env' variable

Florent Xicluna added the comment: Thanks. It should be propagated to 2.7. -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-

[issue7659] Attribute assignment on object() instances raises wrong exception

Antoine Pitrou added the comment: I don't think it's an optimization. The point is that object is mostly meant to be subclassed, not to be used as a glorified dict. -- nosy: +pitrou ___ Python tracker

[issue7659] Attribute assignment on object() instances raises wrong exception

Pascal Chambon added the comment: Allright, I suppose it's some kind of optimization ? We get a proper error when we do : >>> object.test=1 Traceback (most recent call last): File "", line 1, in object.test=1 TypeError: can't set attributes of built-in/extension type 'object' >>> So

[issue7026] test_urllib: unsetting missing 'env' variable

Senthil Kumaran added the comment: Fixed in revision 77367 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

[issue7105] weak dict iterators are fragile because of unpredictable GC runs

Antoine Pitrou added the comment: Committed in r77365 (py3k) and r77366 (3.1). Thank you. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue7026] test_urllib: unsetting missing 'env' variable

Florent Xicluna added the comment: Index: Lib/test/test_urllib.py === --- Lib/test/test_urllib.py (revision 77361) +++ Lib/test/test_urllib.py (working copy) @@ -101,7 +101,7 @@ # Records changes to env vars

[issue7026] test_urllib: unsetting missing 'env' variable

Changes by Florent Xicluna : -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/o

[issue7026] test_urllib: unsetting missing 'env' variable

Florent Xicluna added the comment: Index: Lib/test/test_urllib.py === --- Lib/test/test_urllib.py (revision 77361) +++ Lib/test/test_urllib.py (working copy) @@ -101,7 +101,7 @@ # Records changes to env vars

[issue1658] "RuntimeError: dictionary changed size during iteration" in Tkinter

Florent Xicluna added the comment: > test_urllib > test test_urllib failed -- Traceback (most recent call last): > File "/home/apy/rrun/tmp/autotest/apy/lib/python2.6/test/test_urllib.py", > line 104, in setUp > for k, v in os.environ.iteritems(): > RuntimeError: dictionary changed size du

[issue7026] test_urllib: unsetting missing 'env' variable

Florent Xicluna added the comment: The method does not work as expected. See msg97419: -- Author: Sridhar Ratnakumar (srid) Date: 2010-01-08 18:26 I get this error while running Python 2.6.4 tests (on 64-bit Linux box)

[issue7659] Attribute assignment on object() instances raises wrong exception

Brian Curtin added the comment: The 3.x documentation[1] has this: "object does not have a __dict__, so you can’t assign arbitrary attributes to an instance of the object class." - 2.x doesn't have that same blurb -- it looks like it should. AttributeError vs. TypeError seems to be the issue h

[issue1658] "RuntimeError: dictionary changed size during iteration" in Tkinter

Sridhar Ratnakumar added the comment: I get this error while running Python 2.6.4 tests (on 64-bit Linux box) test_urllib test test_urllib failed -- Traceback (most recent call last): File "/home/apy/rrun/tmp/autotest/apy/lib/python2.6/test/test_urllib.py", line 104, in setUp for k, v in

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15793/issue7092_regrtest_clean.diff ___ Python tracker ___ ___ Python-bugs-

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15790/issue7092_json_sqlite.diff ___ Python tracker ___ ___ Python-bugs-l

[issue7632] dtoa.c: oversize b in quorem

Mark Dickinson added the comment: Here's a patch that seems to fix the problem; I'll wait a while to see if I get a response from David Gay before applying this. Also, if we've got to the stage of modifying the algorithmic part of the original dtoa.c, we should really make sure that we've go

[issue7659] Problems with attribute assignment on object instances

New submission from Pascal Chambon : It seems we can't assign attributes to "objet" class instances, which don't have a __dict__ : IDLE 2.6.4 >>> a = object() >>> a.abc = 3 Traceback (most recent call last): File "", line 1, in a.abc = 3 AttributeError: 'object' object has no attr

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Antoine Pitrou added the comment: About issue7092_json_sqlite.diff: if json produces py3k warnings in normal use (does it?), the warnings should be suppressed in json itself, not in regrtest.py. -- ___ Python tracker

[issue7657] test_ctypes failure on AIX 5.3

Changes by sangamesh : -- keywords: +patch Added file: http://bugs.python.org/file15791/bitfield.patch ___ Python tracker ___ ___ Pytho

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Florent Xicluna added the comment: I split the Big Patch™ into pieces. It should be easier to review and merge. - issue7092_syntax_imports.diff --> Only syntax and import_module(m, deprecated=True) - issue7092_check_warnings.diff --> Use test.test_support.check_warnings() - issue7092

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15789/issue7092_filterwarnings.diff ___ Python tracker ___ ___ Python-bugs-

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15788/issue7092_check_warnings.diff ___ Python tracker ___ ___ Python-bugs-

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Added file: http://bugs.python.org/file15787/issue7092_syntax_imports.diff ___ Python tracker ___ ___ Python-bugs-

[issue2796] Build issues in DragonFly BSD

Brian Curtin added the comment: Can you confirm that this is still an issue on a version >= 2.6? -- nosy: +brian.curtin versions: +Python 2.6 -Python 2.5 ___ Python tracker ___ _

[issue7657] test_ctypes failure on AIX 5.3

Changes by Brian Curtin : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.

[issue7652] Merge C version of decimal into py3k.

Stefan Krah added the comment: Just an update. Rev.77358 should compile and run stable on the buildbot platforms except Alpha and ia64. I'm working on a default ANSI path for 64-bit. -- ___ Python tracker

[issue7652] Merge C version of decimal into py3k.

Stefan Krah added the comment: Unify test_decimal and test_cdecimal: Yes, quite possible. The diff is currently 400 lines, but it should be easy to get that down to below 100 without any loss of functionality. I'll look into that when I'm done with the 64 bit ANSI path. Documentation: Anyt

[issue7643] What is an ASCII linebreak?

Florent Xicluna added the comment: It's confusing. There's a specific annex UAX #14 which defines "Line Breaking Properties". Some properties are defines as "Mandatory Line Breaks (non-tailorable)": BK, CR, LF, NL And the resulting list is different: CA

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ned Deily added the comment: "* The change to LIPO_32BIT_FLAGS is unconditional, the current values are needed to build on modern system, I guess the proposed new value would be needed for building on 10.4?" Ah, yes, sorry. I built and tested with and on 10.6 with 10.5 SDK/gcc-4.0, on

[issue7643] What is an ASCII linebreak?

Michael Foord added the comment: Documenting the characters that splitlines treats as newlines for Unicode should definitely be done. -- ___ Python tracker ___ _

[issue7643] What is an ASCII linebreak?

Florent Xicluna added the comment: Some technical background. == Unicode == According to the Unicode Standard Annex #9, a character with bidirectional class B is a "Paragraph Separator". And “Because a Paragraph Separator breaks lines, there will be at most one per line, at the end of that lin

[issue7651] Python3: guess text file charset using the BOM

STINNER Victor added the comment: New version of the patch which is shorter, cleaner, fix the last bug (seek) and don't change the default behaviour anymore (checking for BOM is now explicit): * BOM checking is now optional (explicit): use open(filename, encoding="BOM"). open(filename, "w", e

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ned Deily added the comment: As far as I can see, the only possible shortcoming of the patch is that it restores the current behavior with a 2-way fat ppc/i386 build with 10.4u (i.e. the way python.org installers are currently built); that is, you would still not be able to use "arch" to sele

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ronald Oussoren added the comment: BTW. The patch is incorrect in it current form: * The change to LIPO_32BIT_FLAGS is unconditional, the current values are needed to build on modern system, I guess the proposed new value would be needed for building on 10.4? * The patch changes pythonw to u

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ronald Oussoren added the comment: Ned: the new functionality is also needed for 2-way univeral binaries, it makes pythonw behave much more as if you execute the real interpreter instead of a stub executable. That posix_spawn doesn't exist sucks, and I'm a bit annoyed with myself for not not

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Martin v. Löwis added the comment: To elaborate, it should be possible to declare the posix_spawnp functions as __attribute__((weak)), and then test at run-time whether the function (pointers) are null. See http://tinyurl.com/y8myawg for an example. -- ___

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ned Deily added the comment: Also, the new functionality is really only needed for 32-bit/64-bit multi-arch builds which aren't support with the 10.4u SDK anyway. -- ___ Python tracker

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target: no spawn.h

Ned Deily added the comment: Not cleanly, I think. The problem is there's no spawn.h in the 10.4u SDK so it can't be built on 10.4 without supplying a copy of a system header file. -- title: OS X pythonw.c compile error with 10.4 or earlier deployment target -> OS X pythonw.c compile

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target

Martin v. Löwis added the comment: Would it be possible to make this a runtime choice? I.e. use posix_spawn when available, and exec otherwise? -- nosy: +loewis ___ Python tracker _

[issue6834] use different mechanism for pythonw on osx

Ned Deily added the comment: Note, r77031 and r77032 cause compile errors for OS X deployment targets of 10.4 or earlier. See Issue7658 for details and patch. -- ___ Python tracker ___

[issue7092] Test suite emits many DeprecationWarnings when -3 is enabled

Changes by Florent Xicluna : Removed file: http://bugs.python.org/file15776/issue7092_Lib_tests_big_patch.diff ___ Python tracker ___ ___ Pyth

[issue7658] OS X pythonw.c compile error with 10.4 or earlier deployment target

New submission from Ned Deily : r77031 (trunk) and r77032 (py3k) for Issue6834 enhanced the the OS X python interpreter launcher, python/pythonw, to allow user-selection of the interpreter execution architecture for multiple architecture builds, i.e. 32-bit vs 64-bit, by using the enhanced capabi

[issue2539] Windows Registry issue with 2.5.2 AMD64 msi

Martin v. Löwis added the comment: Whatever the problem, it seems to have gone away. Closing as out-of-date. -- resolution: -> out of date status: open -> closed ___ Python tracker