Right, as threatened, I've checked in fixes to those two
paper-bag-over-my-head bugs, as well as the new bztar feature, and
release Distutils 0.8.2. Hey wow, that's cool -- technically speaking,
I didn't have to write *any* code for this release -- just check in
patches! Thanks, Lyle and Harry!
Here's the entry from CHANGES.txt:
Release 0.8.2 (24 April, 2000):
-------------------------------
* bug fix: --help option failed due to over-eager refactoring in
0.8.1 (thanks to Harry Henry Gebel)
* bug fix: conversion of Unix-style paths to Windows style fixed
(so the sdist command should be portable now) (thanks to
Lyle Johnson)
* added bztar format to generate .tar.bz2 source distributions
(thanks to Harry Henry Gebel)
--
Greg Ward - just another /P(erl|ython)/ hacker gward(a)python.net
http://starship.python.net/~gward/
I can never remember how to spell "mnemonic".
> BTW, has anyone other than me successfully used the "sdist" command,
> specifically written and processed a MANIFEST.in file, under Windows
> yet?
Looks like there's a bug in the native_path() function and that's why the
forward-slashes in commands like this:
include/autotest.py
don't get translated into Windows-style paths like this:
include\autotest.py
I think once you look at the current implementation of native_path() you'll
see the problem; but I've attached a patch which I think does what you
originally intended there.
Hope this helps,
Lyle
Greg Ward wrote:
[snip]
> But I still don't think this is the place for lists-of-files-built or
> lists-of-file-installed. As it happens, I have made some renovations to
> the code to accomodate this sort of thing; now, you get those list by
> calling the 'get_outputs()' method on the build or install command
> objects. I think the list-of-files-installed really is the property of
> the class that does the installation, and I don't see a big need to keep
> a copy of that list with the "package meta-data" -- yes, this is
> information that should be installed with the meta-data, but it isn't
> really meta-data per se (IMHO).
Perhaps we're quibbling over semantics here: my definition of meta-data is
"information about the package that is installed with the package", in other
words, DistributionMetadata + the installed file list. Since we both seem
to agree that all of this information should be installed with the package,
maybe we should use another term to describe this complete set. Anyway,
this is what PackageInfo attempts to address.
[snip]
> If people want to make RPMs, they will use the "bdist_rpm" command --
> when it exists. ;-) A prototype is "bdist_dumb", which generates a zip
True, and I suppose that if you're using RPMs, you would just use the RPM
command or one of it's many fine graphical wrappers to deal with the RPM
database.
However, I still maintain that is is desirable to have a single interface
that can be specialized to whatever package information repository is
preferred by the system administrator. Consider the case where I have a
number of packages installed using RPM. Now I download a source release and
use (some future version of) the distutils "install" command. Shouldn't
"install" be able to determine whether its dependencies are satisfied from
the RPM packages as well as its own? I'm not saying that we should
implement an RPM front end, just that the interface should be clean and
independent enough so that it could _wrap_ an RPM interface.
[snip]
> Ahh, I thought it was something like that. I'm also starting think your
> original pprint-and-execfile approach was better. Arghh! Maybe a
:-). Well, I still have the original code... Maybe the best way to prove a
point is to implement the alternative.
> syntax with fragments of Python code to define the complicated
> structures would be a good compromise. Hmmm... in any case, I think
> it's moving away from something simple enough for ConfigParser to be
> appropriate.
Actually, I was thinking about something along these lines Friday night
while looking through the funky python-to-english code in the last patch.
The hybrid you've suggested might look something like this:
if is_trivial_string(item):
print '%s: %s' % (attr, item)
else:
print '%s: ',
pprint.pprint(item)
Parsing then just becomes a matter of checking for any special characters at
the beginning of the value (quote, bracket...).
Numbers might cause a problem. You could define a trivial string to exclude
strings that begin with a number, but then what about version numbers?
Should they have to be quoted? Maybe there should just be a special quoting
character around everything but a trivial string. But alas, I'm rambling...
=============================================================================
michaelMuller = mmuller(a)enduden.com | http://www.cloud9.net/~proteus
-----------------------------------------------------------------------------
The natural progress of things is for liberty to yield and government to
gain control. - Thomas Jefferson
=============================================================================
This correct a small error in the distutils.core.setup docstring where it
refers to class Distribution as still being in distutils.core .
--
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware
"Why do you look for the living among the dead?
He is not here, but has risen."
Luke 24:5 (NRSV)
When I tested the bzip2 patch I had bzip after compress, but when I made
the patch I switched them and I forgot to but a comma after bzip2, this
patch has the comma.
--
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware
"Why do you look for the living among the dead?
He is not here, but has risen."
Luke 24:5 (NRSV)
I don't know if anyone is interested, but there is are Distutils RPMs
available at my FTP site:
ftp://pyncurses.sourceforge.net/pub/pyncurses/
Happy Easter!
--
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware
"Why do you look for the living among the dead?
He is not here, but has risen."
Luke 24:5 (NRSV)
I thought some people might find a generic INSTALL file like the one
supplied with programs that use ./configure, here is one I prepared that
gives a few lines with the most-common-case installation instructions and
gives the complete ./setup.py help output.
--
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware
PyNcurses: python binding for ncurses http://pyncurses.sourceforge.net
The --help argument is not working in Distutils v0.8.1 . The problem is
caused by two things: FancyGetopt.generate_help() does not have a self
argument and FancyGetopt.print_help() places the file argument first, but
all the functions that call it seem to expect the header argument to be
first. A patch is attached that fixes the problem.
--
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware
PyNcurses: python binding for ncurses http://pyncurses.sourceforge.net
I thought this would be an appropriate place to mention that the CVS
version of PyNcurses now uses Distutils. The next release (which will be
in a few days) will also use them. Thanks for the great package, if
anybody here uses PyNcurses they can tell you the old method was about as
primitive as they come, now with Distutils it makes things look like I
know what I'm doing ;)
--
Harry Henry Gebel, Senior Developer, Landon House SBS
West Dover Hundred, Delaware
PyNcurses: python binding for ncurses http://pyncurses.sourceforge.net
This release fixes a couple of bugs that people reported in Distutils
0.8, as well as adding two nice features. Here's the change log...
* added the meta-data display options: now you can run the setup
script with --name, --author, --description, etc. and it will
print out that information (thanks to Bastian Kleineidam for
the original idea and patch)
* thoroughly overhauled the distutils.fancy_getopt module to support
those options
* manifest template files can now take many filename patterns per
line (thanks to Andrew Kuchling)
* code cleanup: better and more consistent use of exceptions
* building extensions should now work on AIX, thanks to a hack
that fixes "./ld_so_aix" in Python's installed Makefile
* fixed the "sample3" example to actually work (it hadn't been
updated with the Great Renaming prior to release 0.8)
Greg
You'll find at the usual place:
http://www.python.org/sigs/distutils-sig/download.html
--
Greg Ward - programmer-at-large gward(a)ase.com
http://starship.python.net/~gward/
I'm a nuclear submarine under the polar ice cap and I need a Kleenex!
