"M.-A. Lemburg" <mal(a)lemburg.com> writes:
> Python 1.5.2 is still in active use out there. It's not worth
> breaking code just for cosmetic reasons.
But are these 1.5.2 users going to see any new distutils code?
I.e. do people who still run 1.5.2 occasionally upgrade their
distutils installation? I'd be surprised, but could always be wrong.
It would be a good idea to leave the last 1.5.2 compatible released
distutils tarball somewhere prominent in any case.
Every now and then, Google doesn't throw up what I need so I start
checking Altavista, Yahoo, etc. In almost every single case, I am
brutally reminded why I use Google in the first place.
-- John Riddoch, asr
I came across a strange bug on Win2k, that setup.py
is not included in the distribution by default.
This only occurrs, when the distribution is built by this command line
and not with
python setup.py sdist
The problem is that in the first case the MANIFEST file contains this line:
and this line in the second case:
The cause is that in the first case sys.argv is set to
the absolute path 'c:\\sf\\distutils\\setup.py', in the second
case it is 'setup.py'.
Finally, the sdist command copies it's file list in this way:
dest = os.path.join(base_dir, file)
self.copy_file(file, dest, link=link)
and os.path.join(xxx, yyy) returns yyy when yyy is an absolute path.
The workaround is simple:
- either use the second form to start the setup script,
- or insert 'setup.py' manually in the MANIFEST.in file.
Sounds like a bug to me, but I'm not sure how to fix it.
Should absolute path names in MANIFEST be allowed or not?
>>>>> "AMK" == Andrew Kuchling <akuchlin(a)mems-exchange.org> writes:
AMK> On Tue, Nov 05, 2002 at 12:11:11PM -0800,
AMK> jhylton(a)users.sourceforge.net wrote:
>> Remove use of string module and reflow a couple of long lines.
AMK> Note that the use of string methods means the end of 1.5.2
AMK> compatibility. If we're doing that, then there are many more
AMK> modernizations that can be done to the Distutils code.
Do people sitll care about Python 1.5.2 support moving forward? I'd
propose to make the last distutils release for 1.5.2 the final release
and make distutils conform to modern Python.
I'd like to check in the following patch; it causes unknown keywords
in the setup() invocation to trigger a warning instead of an
exception. This will make it possible to add more metadata arguments
to setup() in future versions while still letting packages be
installed with Distutils versions lacking the added arguments.
Any objections? Should it be backported to Python 2.2?
RCS file: /cvsroot/python/python/dist/src/Lib/distutils/dist.py,v
retrieving revision 1.56
diff -u -u -r1.56 dist.py
--- dist.py 11 Sep 2002 16:31:52 -0000 1.56
+++ dist.py 31 Oct 2002 00:24:55 -0000
@@ -9,7 +9,7 @@
__revision__ = "$Id: dist.py,v 1.56 2002/09/11 16:31:52 jhylton Exp $"
-import sys, os, string, re
+import sys, os, string, re, warnings
from types import *
from copy import copy
from distutils.errors import *
@@ -206,8 +206,7 @@
elif hasattr(self, key):
setattr(self, key, val)
- raise DistutilsSetupError, \
- "invalid distribution option '%s'" % key
+ warnings.warn("Unknown distribution option: %r" % key)