setuptools/EasyInstall 0.6a1 candidate 1 snapshot
This thing's been in limbo too long, so I've made a prerelease snapshot. You can get it with: easy_install -f http://peak.telecommunity.com/snapshots/ setuptools I have fixed all reported bugs, and implemented quite a few new features like MD5 checking (which works even with PyPI's md5 data) and an enhanced "build_ext --inplace" that lets you switch between different Python interpreters without having to recompile your extensions. (The extensions are built in build/, then copied to the source tree whenever you "build_ext" using a different interpreter than the last.) If you have any projects using setuptools, I encourage you to give this snapshot a try, so I can find out if there are still any lurking bugs. If there are no bug reports by next weekend, this will get pushed out as 0.6a1. If you want to look at the documentation, use CVS or browse the EasyInstall.txt, setuptools.txt, and pkg_resources.txt files found at: http://cvs.sourceforge.net/viewcvs.py/python/python/nondist/sandbox/setuptoo... (I just made some changes to these, however, that may take a few hours to update in SourceForge's anonymous CVS.)
On Mon, 22 Aug 2005 02:03 pm, Phillip J. Eby wrote:
I have fixed all reported bugs, and implemented quite a few new features like MD5 checking (which works even with PyPI's md5 data)
Glad you could get things going in spite of PyPI :) I'm going to be busy with PyWeek for the next few weeks. Once that's out of the way, I can do some PyPI stuff if need be (of course, anyone else is free to work on PyPI too... :) Richard
Hi Phillip, Am 22.08.2005 um 06:03 schrieb Phillip J. Eby:
If you have any projects using setuptools, I encourage you to give this snapshot a try, so I can find out if there are still any lurking bugs. If there are no bug reports by next weekend, this will get pushed out as 0.6a1.
I've upgraded to 0.6a1 on one machine, and am now getting the following error for a fresh checkout of my project [1]: $ ./setup.py build Traceback (most recent call last): File "./setup.py", line 23, in ? ez_setup.use_setuptools() File "/usr/local/src/bitten/trunk/ez_setup/__init__.py", line 72, in use_setuptools pkg_resources.require("setuptools>="+version) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 503, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 479, in resolve env = Environment(self.entries) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 558, in __init__ self.scan(search_path) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 588, in scan self.add(dist) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 610, in add if dist not in dists: File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 1760, in __cmp__ def __cmp__(self, other): return cmp(self.hashcmp, other) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 1760, in __cmp__ def __cmp__(self, other): return cmp(self.hashcmp, other) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 1755, in <lambda> lambda self: ( File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 1782, in parsed_version self._parsed_version = pv = parse_version(self.version) File "/usr/lib/python2.3/site-packages/setuptools-0.6a1- py2.3.egg/pkg_resources.py", line 1797, in version raise ValueError( ValueError: ("Missing 'Version:' header and/or PKG-INFO file", bitten [unknown version] (/usr/local/src/bitten/trunk)) Previously I've been using 0.5a13. The project includes ez_setup as svn:external. Is this a problem in (or incompatibility with) ez_setup? Thanks, Chris [1] http://bitten.cmlenz.net/ -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/
At 03:09 PM 8/22/2005 +0200, Christopher Lenz wrote:
I've upgraded to 0.6a1 on one machine, and am now getting the following error for a fresh checkout of my project [1]: ... raise ValueError( ValueError: ("Missing 'Version:' header and/or PKG-INFO file", bitten [unknown version] (/usr/local/src/bitten/trunk))
Is there a /usr/local/src/bitten/trunk/bitten.egg-info/PKG-INFO file, with a 'Version:' header in it? If not, then the error message is correct, and you should go to /usr/local/src/bitten/trunk and run "setup.py egg_info" to rebuild the project's egg-info.
Previously I've been using 0.5a13. The project includes ez_setup as svn:external. Is this a problem in (or incompatibility with) ez_setup?
No; it just looks like a straightforward error to me. Older versions of pkg_resources (like the 0.5 versions) sometimes masked this error, though, as it used to be an AttributeError instead of a ValueError, and it could thus get suppressed in certain situations.
Am 22.08.2005 um 15:55 schrieb Phillip J. Eby:
At 03:09 PM 8/22/2005 +0200, Christopher Lenz wrote:
I've upgraded to 0.6a1 on one machine, and am now getting the following error for a fresh checkout of my project [1]: ... raise ValueError( ValueError: ("Missing 'Version:' header and/or PKG-INFO file", bitten [unknown version] (/usr/local/src/bitten/trunk))
Is there a /usr/local/src/bitten/trunk/bitten.egg-info/PKG-INFO file, with a 'Version:' header in it? If not, then the error message is correct, and you should go to /usr/local/src/bitten/ trunk and run "setup.py egg_info" to rebuild the project's egg-info.
Running "setup.py egg_info" results in exactly the error I posted. A chicken and egg problem, I suppose. ;-) Note that the error is raised from the "ez_setup.use_setuptools()" call in setup.py. If I just import setuptools without going through ez_setup, everything works fine. Am I missing something? Thanks, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/
At 04:30 PM 8/22/2005 +0200, Christopher Lenz wrote:
Am 22.08.2005 um 15:55 schrieb Phillip J. Eby:
At 03:09 PM 8/22/2005 +0200, Christopher Lenz wrote:
I've upgraded to 0.6a1 on one machine, and am now getting the following error for a fresh checkout of my project [1]: ... raise ValueError( ValueError: ("Missing 'Version:' header and/or PKG-INFO file", bitten [unknown version] (/usr/local/src/bitten/trunk))
Is there a /usr/local/src/bitten/trunk/bitten.egg-info/PKG-INFO file, with a 'Version:' header in it? If not, then the error message is correct, and you should go to /usr/local/src/bitten/ trunk and run "setup.py egg_info" to rebuild the project's egg-info.
Running "setup.py egg_info" results in exactly the error I posted. A chicken and egg problem, I suppose. ;-)
Note that the error is raised from the "ez_setup.use_setuptools()" call in setup.py. If I just import setuptools without going through ez_setup, everything works fine. Am I missing something?
No, it probably just means that I need to change the above code to issue a warning instead of an error and treat the version as '' in that case. When it was trapped as an AttributeError, there was no way to find the problem, but this makes it clear that *not* trapping the error is also a problem. So I guess I'll have to change it to issue a warning instead.
There were bug reports about bdist_rpm, and some issues installing on SuSE Linux, which has a patched version of distutils for no particular reason (that Google knows about, anyway). In the process of fixing these, I found some other problems and went ahead and fixed those too. So, there's now an 0.6a1c2 snapshot you can use, via the instructions below. Please let me know about any problems; if everything looks good, we'll go to 0.6a1 sometime next week. At 12:03 AM 8/22/2005 -0400, Phillip J. Eby wrote:
This thing's been in limbo too long, so I've made a prerelease snapshot. You can get it with:
easy_install -f http://peak.telecommunity.com/snapshots/ setuptools
I have fixed all reported bugs, and implemented quite a few new features like MD5 checking (which works even with PyPI's md5 data) and an enhanced "build_ext --inplace" that lets you switch between different Python interpreters without having to recompile your extensions. (The extensions are built in build/, then copied to the source tree whenever you "build_ext" using a different interpreter than the last.)
If you have any projects using setuptools, I encourage you to give this snapshot a try, so I can find out if there are still any lurking bugs. If there are no bug reports by next weekend, this will get pushed out as 0.6a1. If you want to look at the documentation, use CVS or browse the EasyInstall.txt, setuptools.txt, and pkg_resources.txt files found at:
http://cvs.sourceforge.net/viewcvs.py/python/python/nondist/sandbox/setuptoo...
(I just made some changes to these, however, that may take a few hours to update in SourceForge's anonymous CVS.)
participants (3)
-
Christopher Lenz -
Phillip J. Eby -
Richard Jones