Re: [Python-Dev] 2.4.4: backport classobject.c HAVE_WEAKREFS?
Hi Fredrik, On Fri, Oct 13, 2006 at 11:22:09AM +0200, Fredrik Lundh wrote: > > > static PyTypeObject NoddyType; > > static PyTypeObject *NoddyType; > > yeah, that's a silly typo. Ah, then ignore my previous remark. Armin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.3.6 for the unicode buffer overrun
Martin v. Löwis wrote: > Steve Holden schrieb: > The other thing to watch out for is that I (or whoever) can still do local work on a bunch of different files >>> >>>the point of my previous post is that you *shouldn't* have to edit a >>>bunch of different files to make a new release. >>> >> >>Indeed. I seem to remember suggesting a while ago on pydotorg that >>whatever replaces pyramid should cater to groups such as the release >>team by allowing everything necessary to be generated from a simple set >>of data that wouldn't be difficult to maintain. Anthony has enough on >>his plate without having to fight the web server too ... > > > There is always some sort of text that accompanies a release. That has > to be edited to be correct; a machine can't do that. > OK. ^everything^the content structure and many of the files^ regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://holdenweb.blogspot.com Recent Ramblings http://del.icio.us/steve.holden ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] VC6 support on release25-maint
Hello. I noticed VisualC++6 support came back. I'm glad with that, but still it seems incomplete. (for example, _sqlite3 support) Maybe does this patch help process? On my machine, testcases other than distutils runs fine. http://sourceforge.net/tracker/?func=detail&aid=1457736&group_id=5470&atid=305470 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.3.6 for the unicode buffer overrun
On Sunday 15 October 2006 21:23, Steve Holden wrote: > Martin v. Löwis wrote: > > Steve Holden schrieb: > The other thing to watch out for is that I (or whoever) can still do > local work on a bunch of different files > >>> > >>>the point of my previous post is that you *shouldn't* have to edit a > >>>bunch of different files to make a new release. > >> > >>Indeed. I seem to remember suggesting a while ago on pydotorg that > >>whatever replaces pyramid should cater to groups such as the release > >>team by allowing everything necessary to be generated from a simple set > >>of data that wouldn't be difficult to maintain. Anthony has enough on > >>his plate without having to fight the web server too ... > > > > There is always some sort of text that accompanies a release. That has > > to be edited to be correct; a machine can't do that. > > OK. > > ^everything^the content structure and many of the files^ If you compare the various pieces that make up the release pages, you'll see that much of it is boilerplate, true. There's two cases worth mentioning: First release of a new series (2.4.4c1, 2.5a1). This involves making the new directory and all the little fiddly files. In practice, this is done by recursively copying the previous release and removing the .ssh directories so that it can be re-added. I then go through and update the files. Subsequent release. This is still largely a manual process - I search for all the references to the previous release, update them, then read through it for missed bits. I then update the text bits that need to be changed. There's all sorts of minor variations there - for instance, often in a non-final release, we don't have an unpacked version of the documentation (but sometimes we do, wah). The killer bits for me are all the other places. For instance, updating the sidebar menu quicklinks for 2.4.4 to 2.5. There's just too many files, and the structure of pyramid's files still doesn't make sense to me. Anthony -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] 2.3.6 for the unicode buffer overrun
Anthony Baxter schrieb: > Subsequent release. This is still largely a manual process - I search for all > the references to the previous release, update them, then read through it for > missed bits. I then update the text bits that need to be changed. There's all > sorts of minor variations there - for instance, often in a non-final release, > we don't have an unpacked version of the documentation (but sometimes we do, > wah). If that's a source of pain, we can standardize (assuming you are talking about the .chm file). Which way would you like it? It really doesn't matter to me either way - I just didn't think of it causing problems. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] VC6 support on release25-maint
ocean schrieb: > Hello. I noticed VisualC++6 support came back. I'm glad with that, > but still it seems incomplete. (for example, _sqlite3 support) Maybe > does this patch help process? These changes were all contributed by Larry Hastings. For some reason, I missed/forgot about your patch. Can you please update it? Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Cloning threading.py using proccesses
Fredrik Lundh schrieb: > but given that the format *has* been stable for many years, surely it > would make more sense to just codify that fact, rather than developing > Yet Another Serialization Format instead? There have been minor changes over time, e.g. r26146 (gvanrossum) introduced TYPE_TRUE and TYPE_FALSE, r36242 (loewis) introduced TYPE_INTERNED and TYPE_STRINGREF, and r38266 (rhettinger) introduced TYPE_SET and TYPE_FROZENSET. With these changes, old dumps can load in new versions, but not vice versa. Furthermore, r27219 (nnorwitz) changed the co_argcount, co_nlocals, co_stacksize, co_flags, and co_firstlineno fields from short to long; unmarshalling from an old version would just crash/read garbage. So how would you propose to deal with such changes in the future? Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] os.utime on directories: bug fix or new feature?
In Python 2.5.0 and earlier, it is not possible to modify the time stamps of a directory (mtime and atime) on Windows. The reason is that you cannot "open" (CreateFile) a directory. On W9x, it isn't possible, period. On WNT+, it's possible if you pass FILE_FLAG_BACKUP_SEMANTICS to CreateFile. I just applied patch #1576166 to the trunk which does that. Should I backport the patch to 2.5, as it is a bug that you can modify the time stamps of regular files but not directories? Or should I not backport as it is a new feature that you can now adjust the time stamps of a directory, and couldn't before? Anthony, can you please pronounce? Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] os.utime on directories: bug fix or new feature?
On Sun, Oct 15, 2006, "Martin v. L?wis" wrote: > > Should I backport the patch to 2.5, as it is a bug that you can modify > the time stamps of regular files but not directories? Or should I > not backport as it is a new feature that you can now adjust the time > stamps of a directory, and couldn't before? My vote is that it's a bugfix but should be treated as a new feature and rejected for 2.5, based on the standard argument about capabilities and the problems with bugfix releases having new capabilities. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "If you don't know what your program is supposed to do, you'd better not start writing it." --Dijkstra ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] os.utime on directories: bug fix or new feature?
On Sunday 15 October 2006 23:35, Aahz wrote: > On Sun, Oct 15, 2006, "Martin v. L?wis" wrote: > > Should I backport the patch to 2.5, as it is a bug that you can modify > > the time stamps of regular files but not directories? Or should I > > not backport as it is a new feature that you can now adjust the time > > stamps of a directory, and couldn't before? > > My vote is that it's a bugfix but should be treated as a new feature and > rejected for 2.5, based on the standard argument about capabilities and > the problems with bugfix releases having new capabilities. Since it wasn't possible in earlier than 2.5 either, I'd say it's on the edge of being a bugfix. Let's be conservative and not backport it, since it's also a pretty marginal feature. Anthony -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Problem building module against Mac Python 2.4 and Python 2.5
This may be down to my lack of knowledge of Mac OS X development. I want to build my python extension for Python 2.3, 2.4 and 2.5 on the same Mac. Build Python 2.3 and Python 2.4 has been working well for a long time. But after I installed Python 2.5 it seems that I can no longer link a against Python 2.4 without changing sym link /Library/Frameworks/Python.framework/ Versions/Current to point at the one I want to build against. The problem did not arise with Python 2.3 and Python 2.4 because Python 2.3 is in /System/Library and Python 2.4 is in /LIbrary. Telling ld which framework folder to look in allows both to be linked against. Is there a way to force ld to use a particular version of the python framework or do I have to change the symlink each time I build against a different version? This type of problem does not happen on Windows or Unix by design. Barry ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Problem building module against Mac Python 2.4 and Python 2.5
On 10/15/06, Barry Scott <[EMAIL PROTECTED]> wrote: > This may be down to my lack of knowledge of Mac OS X development. > > I want to build my python extension for Python 2.3, 2.4 and 2.5 on > the same Mac. > Build Python 2.3 and Python 2.4 has been working well for a long > time. But > after I installed Python 2.5 it seems that I can no longer link a > against Python 2.4 > without changing sym link /Library/Frameworks/Python.framework/ > Versions/Current > to point at the one I want to build against. > > The problem did not arise with Python 2.3 and Python 2.4 because > Python 2.3 > is in /System/Library and Python 2.4 is in /LIbrary. Telling ld which > framework > folder to look in allows both to be linked against. > > Is there a way to force ld to use a particular version of the python > framework or do > I have to change the symlink each time I build against a different > version? > > This type of problem does not happen on Windows or Unix by design. Use an absolute path to the library rather than -framework. Or use distutils! -bob ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Problem building module against Mac Python 2.4 and Python 2.5
On Oct 15, 2006, at 9:41 PM, Bob Ippolito wrote: On 10/15/06, Barry Scott <[EMAIL PROTECTED]> wrote: This may be down to my lack of knowledge of Mac OS X development. I want to build my python extension for Python 2.3, 2.4 and 2.5 on the same Mac. Build Python 2.3 and Python 2.4 has been working well for a long time. But after I installed Python 2.5 it seems that I can no longer link a against Python 2.4 without changing sym link /Library/Frameworks/Python.framework/ Versions/Current to point at the one I want to build against. The problem did not arise with Python 2.3 and Python 2.4 because Python 2.3 is in /System/Library and Python 2.4 is in /LIbrary. Telling ld which framework folder to look in allows both to be linked against. Is there a way to force ld to use a particular version of the python framework or do I have to change the symlink each time I build against a different version? This type of problem does not happen on Windows or Unix by design. Use an absolute path to the library rather than -framework. That is, add '/Library/Frameworks/Python.framework/Versions/2.4/ Python' to the link command instead of '-framework Python'. Or use distutils! That's definitely advisable anyway, that way you'll automaticly get the right flags to compile and link the extension :-) Ronald smime.p7s Description: S/MIME cryptographic signature ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Weekly Python Patch/Bug Summary
Patch / Bug Summary ___ Patches : 431 open ( +3) / 3425 closed ( +8) / 3856 total (+11) Bugs: 916 open (-23) / 6273 closed (+44) / 7189 total (+21) RFE : 244 open ( +4) / 240 closed ( +1) / 484 total ( +5) New / Reopened Patches __ typo in PC/_msi.c (2006-10-07) CLOSED http://python.org/sf/1572724 opened by jose nazario Fix for segfault in ISO 2022 codecs (2006-10-07) CLOSED http://python.org/sf/1572832 opened by Ray Chason let quit and exit really exit (2006-10-09) CLOSED http://python.org/sf/1573835 opened by Gerrit Holl urllib2 - Fix line breaks in authorization headers (2006-10-09) http://python.org/sf/1574068 opened by Scott Dial Add %var% support to ntpath.expandvars (2006-10-09) http://python.org/sf/1574252 opened by Chip Norkus Mailbox will lock properly after flush() (2006-10-11) http://python.org/sf/1575506 opened by Philippe Gauthier Support spawnvp[e] + use native execvp[e] on win32 (2006-10-12) http://python.org/sf/1576120 opened by Snaury os.utime acess denied with directories on win32 (2006-10-12) CLOSED http://python.org/sf/1576166 opened by Snaury os.execvp[e] on win32 fails for current directory (2006-10-13) http://python.org/sf/1576313 opened by Snaury Fix VC6 build, remove redundant files for VC7 build (2006-10-14) CLOSED http://python.org/sf/1576954 opened by Larry Hastings Fix VC6 build, remove redundant files for VC7 build (2006-10-14) CLOSED http://python.org/sf/1577078 opened by Larry Hastings Add _ctypes, _ctypes_test, and _elementtree to VC6 build (2006-10-15) CLOSED http://python.org/sf/1577551 opened by Larry Hastings newline in -DSVNVERSION=\"`LANG=C svnversion .`\" (2006-10-15) CLOSED http://python.org/sf/1577756 opened by Daniel Stränger Patches Closed __ typo in PC/_msi.c (2006-10-07) http://python.org/sf/1572724 closed by gbrandl Fix for segfault in ISO 2022 codecs (2006-10-08) http://python.org/sf/1572832 closed by perky fix crash with continue in nested try/finally (2006-08-18) http://python.org/sf/1542451 closed by gbrandl let quit and exit really exit (2006-10-09) http://python.org/sf/1573835 closed by mwh Fix for Lib/test/crashers/gc_inspection.py (2006-07-04) http://python.org/sf/1517042 closed by gbrandl os.utime acess denied with directories on win32 (2006-10-12) http://python.org/sf/1576166 closed by loewis Fix VC6 build, remove redundant files for VC7 build (2006-10-14) http://python.org/sf/1576954 closed by loewis Fix VC6 build, remove redundant files for VC7 build (2006-10-14) http://python.org/sf/1577078 deleted by lhastings Add _ctypes, _ctypes_test, and _elementtree to VC6 build (2006-10-15) http://python.org/sf/1577551 closed by loewis newline in -DSVNVERSION=\"`LANG=C svnversion .`\" (2006-10-15) http://python.org/sf/1577756 deleted by schmaller New / Reopened Bugs ___ cElementTree.SubElement doesn't recognize keyword "attrib" (2006-10-07) CLOSED http://python.org/sf/1572710 opened by Mark Stephens import org.python.core imports local org.py (2006-10-08) CLOSED http://python.org/sf/1573180 opened by E.-O. Le Bigot ctypes unit test fails (test_macholib.py) under MacOS 10.4.7 (2006-08-21) CLOSED http://python.org/sf/1544102 reopened by ronaldoussoren struct module doesn't use weakref for cache (2006-10-08) CLOSED http://python.org/sf/1573394 opened by Mark Flacy sqlite3 documentation on rowcount is contradictory (2006-10-10) http://python.org/sf/1573854 opened by Seo Sanghyeon if(status = ERROR_MORE_DATA) (2006-10-09) CLOSED http://python.org/sf/1573928 opened by Helmut Grohne WSGI, cgi.FieldStorage incompatibility (2006-10-09) http://python.org/sf/1573931 opened by Michael Kerrin isinstance swallows exceptions (2006-10-09) http://python.org/sf/1574217 opened by Brian Harring os.popen with os.close gives error message (2006-10-10) http://python.org/sf/1574310 opened by dtrosset Error with callback function and as_parameter with NumPy ndp (2006-10-10) http://python.org/sf/1574584 opened by Albert Strasheim ctypes: Pointer-to-pointer unchanged in callback (2006-10-10) http://python.org/sf/1574588 opened by Albert Strasheim ctypes: Returning c_void_p from callback doesn't work (2006-10-10) http://python.org/sf/1574593 opened by Albert Strasheim Request wave support > 16 bit samples (2006-10-11) http://python.org/sf/1575020 opened by Murray Lang isSequenceType returns True for dict subclasses (<> 2.3) (2006-10-11) http://python.org/sf/1575169 opened by Martin Gfeller typo: section 2.1 -> property (2006-10-12) CLOSED http://python.org/sf/1575746 opened by Antoine De Groote Missing notice on environment setting LD_LIBRARY_PATH (2006-10-12) CLOSED http://python.or
