Mailman 3 August 2007 - Python-Dev

Cannot build new documentation
by Amaury Forgeot d'Arc Aug. 21, 2007

Aug. 21, 2007

Hello, Martin v. Löwis wrote: > I think the obvious thing you missed is that the problem got fixed > already. Whether the documentation system should be more defensive and > work with 2.5.0 also is a different question. <red of confusion>You are right. python 2.5.1 corrected this. May I still dare propose the following patch: Index: Doc/tools/sphinx-build.py =================================================================== --- Doc/tools/sphinx-build.py (revision 57158) +++ … [View More]

2 1

Cygwin: Problem detecting subprocess termination after _spawn_posix in distutils?
by Steve Holden Aug. 21, 2007

Aug. 21, 2007

I've been trying to install PIL 1.1.6 for several days now under Cygwin. I have tried the Cygwin, Image and distutils lists with nary a pointer, so I wondered whether python-dev might lead me to an answer (other than "Stop using Cygwin" ;-) Here's the output from a failed setup run with a couple of debug prints inserted which should report how sub-process termination occurred - it hangs after this output. $ python setup.py build running build running build_py running build_ext building '… [View More]_imaging' extension SPAWN: ['gcc', '-fno-strict-aliasing', '-DNDEBUG', '-g', '-O3', '-Wall', '-Wstrict-prototypes', '-DHAVE_LIBZ', '-IlibImaging', '-I/usr/include', '-I/usr/include/python2.5', '-c', 'libImaging/Chops.c', '-o', 'build/temp.cygwin-1.5.24-i686-2.5/libImaging/Chops.o'] PATH? 1 V: 0 D:0 gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DHAVE_LIBZ -IlibImaging -I/usr/include -I/usr/include/python2.5 -c libImaging/Chops.c -o build/temp.cygwin-1.5.24-i686-2.5/libImaging/Chops.o Are we done yet? Waiting on pid 3280 I have to kill a python.exe process that's left running in the background if I CTRL/C the build. Otherwise it will spend all night in a tight loop. The compilation is finished when I kill the process, and the next compile will begin if I repeat the command. I extracted the _spawn_all function from distutils/spawn.py, hacked some exceptions and ran it under command line control. That worked fine with other subtasks, so I wondered whether this was a failure specific to gcc, which would seem kind of unlikely. I ran the same compile using my test function standing alone, seeing success: sholden@bigboy ~/Imaging-1.1.6 $ python ~/Projects/Python/spawntest.py gcc -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -DHAVE_LIBZ -IlibImaging -I/usr/include -I/usr/include/python2.5 -c libImaging/Chops.c -o build/temp.cygwin-1.5.24-i686-2.5/libImaging/Chops.o Are we done yet? Waiting on pid 3244 Got pid, status 3244 0 Got WIFEXITED 0 So it appears unlikely to be gcc-specific, leaving me wondering what exactly is the difference between the build environment and my tests. It would be really nice if test_distutils showed any failures, but it doesn't so any assistance would be welcome. At this point I can't even replicate the failure in a simpler test :-( regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://del.icio.us/steve.holden --------------- Asciimercial ------------------ Get on the web: Blog, lens and tag the Internet Many services currently offer free registration ----------- Thank You for Reading ------------- [View Less]

2 5

Cannot build new documentation
by Amaury Forgeot d'Arc Aug. 20, 2007

Aug. 20, 2007

Hello, The new documentation system is really a major improvement: congratulations! However, I run into a problem while trying to build the new python docs. I initially used python2.5 on windows, but Linux seems to have the same problem. Am I really the only one who gets this error? The offending code is in Doc\tools\sphinx\builder.py, and looks like this: >>> from __future__ import with_statement >>> import codecs >>> with codecs.open('foo.txt', 'w', 'utf-8') as … [View More]

2 1

Planning to switch to new tracker on August 23rd
by Brett Cannon Aug. 20, 2007

Aug. 20, 2007

Having squashed the final issues, we are now ready to switch over to the new tracker! The plan is to do it on the 23rd. But before I announce to the community I wanted to make sure there was not some specific objection by python-dev or python-3000. If there is please let me know by midday Monday so that we can postpone to next week if needed. -Brett

1 0

Weekly Python Patch/Bug Summary
by Kurt B. Kaiser Aug. 19, 2007

Aug. 19, 2007

Patch / Bug Summary ___________________ Patches : 417 open (+13) / 3855 closed ( +0) / 4272 total (+13) Bugs : 1069 open ( +4) / 6800 closed (+10) / 7869 total (+14) RFE : 262 open ( -1) / 296 closed ( +1) / 558 total ( +0) New / Reopened Patches ______________________ Replacing char* with const char* (2007-08-12) http://python.org/sf/1772673 opened by eXt [python-mode] Properly highlight lambda with no arguments (2007-08-12) http://python.org/sf/1772721 … [View More]

1 0

Summary of Tracker Issues
by Tracker Aug. 19, 2007

Aug. 19, 2007

ACTIVITY SUMMARY (08/12/07 - 08/19/07) Tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 1300 open ( +5) / 11141 closed ( +0) / 12441 total ( +5) Average duration of open issues: 694 days. Median duration of open issues: 553 days. Open Issues Breakdown open 1300 ( +5) pending 0 ( +0) Issues Created Or Reopened (5) ______________________________ Test … [View More]

1 0

PEP 11 update - Call for port maintainers to step forward
by skip＠pobox.com Aug. 18, 2007

Aug. 18, 2007

I made a quick update to PEP 11, "Removing support for little used platforms". I added details about ending support for AtheOS/Syllable and BeOS. I also added a yet-to-be-fleshed out section entitled "Platform Maintainers". I intend that to the extent possible we document the responsible parties for various platforms. Obviously, common platforms like Windows, Mac OS X, Linux and common Unix platforms (Solaris, *BSD, what else?) will continue to be supported by the core Python developer … [View More]

1 0

sys.last_traceback - annoying pdb behaviour
by Alexander Schremmer Aug. 18, 2007

Aug. 18, 2007

Hi there, when I tried to use pdb, I spotted some kind of annoying behaviour of pdb: for pdb.pm, it still uses sys.last_traceback which is set by code.py This renders the function unusable in non-interactive contexts ... I suggest to change pdb.pm to use sys.exc_traceback instead. Any reasons not to do so? For Py3k, it might make sense to kill it completly. Besides that, some other places in the stdlib reference this attr as well: idle in 5 places ./lib-tk/Tkinter.py: … [View More]

3 3

sys.last_traceback - annoying pdb.pm behaviour
by Alexander Schremmer Aug. 18, 2007

Aug. 18, 2007

Hi there, when trying to use pdb, I spotted some kind of annoying behaviour of pdb: for pdb.pm, it still uses sys.last_traceback which is set by code.py This renders the function unusable in non-interactive contexts ... I suggest to change pdb.pm to use sys.exc_traceback instead. Any reasons not to do so? For Py3k, it might make sense to kill it. Besides that, some other places in the stdlib reference this attr as well: idle in 5 places ./lib-tk/Tkinter.py: sys.last_traceback = tb ./… [View More]

1 0

Source file markers for Tru64?
by skip＠pobox.com Aug. 18, 2007

Aug. 18, 2007

I'm working on removing Tru64 support from the Python 3 code base. There aren't that many markers which actually say "Tru64". I see __digitial__ and OSF/1 as well. What others are there? Thx, Skip

4 10