Considering the following schedule of events: Oct 4: I go out of town (away from email, off the net, etc.) Oct 10: planned release of Python 2.0 Oct 12: I'm back in town, ready to hack! (and wondering why it's so quiet around here...) the Distutils 1.0 release will go out October 1 or 2. I don't need quite as much code freeze time as the full Python release, but let's put it this way: if there are features you want added to the Distutils that I don't already know about, forget about it. Changes currently under consideration: * Rene Liebscher's rearrangement of the CCompiler classes; most of this is just reducing the amount of code, but it does add some minor features, so it's under consideration. * making byte-compilation more flexible: should be able to generate both .pyc and .pyo files, and should be able to do it at build time or install time (developer's and packager's discretion) If you know about any outstanding Distutils bugs, please tell me *now*. Put 'em in the SourceForge bug database if you're wondering why I haven't fixed them yet -- they might have gotten lost, I might not know about 'em, etc. If you're not sure, put it in SourceForge. Stuff that will definitely have to wait until after 1.0: * a "test" command (standard test framework for Python modules) * finishing the "config" command (auto-configuration) * installing package meta-data, to support "what *do* I have installed, anyways?" queries, uninstallation, upgrades, etc. Blue-sky projects: * standard documentation processing * intra-module dependencies Greg -- Greg Ward gward@python.net http://starship.python.net/~gward/
On Tue, Sep 26, 2000 at 08:53:12PM -0400, Greg Ward wrote:
If you know about any outstanding Distutils bugs, please tell me *now*.
How about the directory caching problem when doing multiple builds in a single Python process? (Reported by me in http://www.python.org/pipermail/distutils-sig/2000-September/001915.html) I'm willing to write a patch, if given guidance on what to write. --amk
On 26 September 2000, Andrew Kuchling said:
How about the directory caching problem when doing multiple builds in a single Python process?
Yep, that one slipped through the cracks all right -- thanks!
(Reported by me in http://www.python.org/pipermail/distutils-sig/2000-September/001915.html) I'm willing to write a patch, if given guidance on what to write.
grep dir_util.py for '_path_cache'. Couldn't hurt to grep *.py, but if any other module is referring to a leading-underscore variable, somebody needs to be slapped with the proverbial wet noodle! ... lessee... yep, just 'mkpath()' and 'remove_tree()' use it. Both will probably need to be changed to use absolute paths. Shouldn't be hard, and I approve. Go for it. Greg
If you know about any outstanding Distutils bugs, please tell me *now*. Put 'em in the SourceForge bug database if you're wondering why I haven't fixed them yet -- they might have gotten lost, I might not know about 'em, etc. If you're not sure, put it in SourceForge.
Mike Fletcher found a another bug: Building extensions on windows (at least with MSVC) in debug mode link with the wrong python import library. This leads to crashes because the extension loads the wrong python dll at runtime. Will report this on sourceforge, although I doubt Greg will be able to fix this... Distutils code freeze: Greg, I have some time next week to work on this. Do you give me permission to check it in if I find a solution? Thomas
On 28 September 2000, Thomas Heller said:
Will report this on sourceforge, although I doubt Greg will be able to fix this...
Distutils code freeze: Greg, I have some time next week to work on this. Do you give me permission to check it in if I find a solution?
Gee, I never replied to this, did I! Did the bug get fixed? Or is it still there in 1.0? Since I'm going to be off the 'net from now until well after Python 2.0 is released, I'm very reluctant to say, "Go ahead, check it in!" -- I don't mind if Python 2.0 goes out with Distutils 1.0.1 (as opposed to 1.0), but I do mind if I'm not there to manage the 1.0.1 release. Tell you what: I'll try to login and check my mail sometime this weekend (Oct 7-8). If there is a clear, obvious, well-understood, well-tested, and approved-by-Thomas (and preferably at least one other Windows-based Distutils hacker) fix for this bug, then I will do my damndest to put together Distutils 1.0.1. If there are any other glaring, show-stopping bugs in Distutils 1.0, they are also be subject to this ruling. (If you have to stand on your hands and hit escape-meta-alt-control-shift-F13 while staring at the screen cross-eyed to get a traceback, the bug probably *won't* be fixed.) If I'm unable to get a couple of uninterrupted hours this weekend, then Python 2.0 will go out with Distutils 1.0 as-is. This is the likely scenario, given my plans for the weekend. ;-) Greg -- Greg Ward gward@python.net http://starship.python.net/~gward/
participants (3)
-
Andrew Kuchling -
Greg Ward -
Thomas Heller