New submission from Sridhar Ratnakumar <sridharr(a)activestate.com>:
> easy_install TracAddHeadersPlugin
Searching for TracAddHeadersPlugin
No local packages or download links found for TracAddHeadersPlugin
Best match: None
Traceback (most recent call last):
File "/Users/sridharr/.local/bin/easy_install", line 8, in <module>
load_entry_point('setuptools==0.6c11', 'console_scripts', 'easy_install')()
packages/setuptools/command/easy_install.py", line 1712, in main
packages/setuptools/command/easy_install.py", line 1700, in with_ei_usage
packages/setuptools/command/easy_install.py", line 1716, in <lambda>
py", line 152, in setup
py", line 975, in run_commands
py", line 995, in run_command
packages/setuptools/command/easy_install.py", line 211, in run
self.easy_install(spec, not self.no_deps)
packages/setuptools/command/easy_install.py", line 434, in easy_install
packages/setuptools/package_index.py", line 475, in fetch_distribution
return dist.clone(location=self.download(dist.location, tmpdir))
AttributeError: 'NoneType' object has no attribute 'clone'
title: AttributeError: 'NoneType' object has no attribute 'clone'
Setuptools tracker <setuptools(a)bugs.python.org>
I know we are not supposed to have a look at the content of the
file and that buildout managed this by itself, but I took a look at it
I found something, which looks strange at the first glance, and I wondered
can any problem (or if I should _really_ let buildout handle this...). At
end of the file, there are a bunch of lines like this::
parts = database i18n test doc ...
(actually, more than thirty). Those which have "parts" have different those
parts in different order each one; there are some with
with a value and some with no value, despite there isn't any more developed
component in the develop option of our configuration file.
So, I wonder: is it normal or not?
Actually, I ask this question, since we had a strange behavior this
there were some components which where still used as developed components,
despite the fact that they have been removed from the buildout
file some hours ago (and some buildout execution latter) (there were still
lying in the develop-eggs/ directory), and I was a bit astonished to find
there were still values in .installed.cfg which referred to those developed
We will have a sprint sunday afternoon, starting at 3 pm in
Berlin/Germany. If you are interested you can join online in the irc
(#distutils on Freenode)
or in Berlin of course.
This sprint will continue the work we've started on the 0.7 branch. If
you have worked during the first sprint and you can't make it sunday,
please make sure your worked was commited in the Distribute repository
with notes so we can continue.
Tarek Ziadé | http://ziade.org | オープンソースはすごい! | 开源传万世，因有你参与
-----BEGIN PGP SIGNED MESSAGE-----
Why would a "bootstrap" fail due to missing / less-than-required version
of setuptools in the host python? The bootstrap should be
self-contained enough to make things work no matter what, since the
point is too build an environment which doesn't rely on anything beyond
a "bare" Python install.
$ svn co $ZSVN/Acquisition/trunk Aq-trunk
$ cd Aq-trun
$ /path/to/python2.6 bootstrap/bootstrap.py
The required version of setuptools (>=0.6c11) is not available, and
can't be installed while this script is running. Please install
a more recent version first, using 'easy_install -U setuptools'.
Tres Seaver +1 540-429-0999 tseaver(a)palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
I just did
on fedora F11 x86_64. I was surprised that it did not build from source,
instead d/l somebody's blist.so.
No surprise, testing 'import blist' fails with an undefined symbol.
This is distribute 0.6.7. Please add option to force build from source.
Sorry, that was meant to go to the list, not as a personal comment to Tarek.
2009/11/2 Paul Moore <p.f.moore(a)gmail.com>:
> 2009/11/2 Tarek Ziadé <ziade.tarek(a)gmail.com>:
> (original quote here from PJE)
>>>> (Personally, I like them just fine where
>>>> they are. Among other things it makes it easy for someone to answer the
>>>> ticket via email, which is one of the reasons I asked for it to be set
>>>> up this way in the first place.)
>> I don't remember you asking in Distutils-SIG to the people if they
>> were OK with that.
> Can we please avoid this flaring up into another Tarek vs PJE fight?
> FWIW, I'm mildly annoyed by setuptools tracker emails appearing here,
> but I live with it. I suggest others do the same.
On behalf of the Distribute team, I am pleased to announce the 0.6.7
release of Distribute.
As usual, availabe at PyPI: http://pypi.python.org/pypi/distribute
Most noticeable changes in 0.6.7 are:
- now the develop command supports the --user option, so it can use
the per-user site packages (PEP 370)
- the generated scripts now wrap their call to the script entry point
in the standard "if name == 'main'"
- better errors handling in PackageIndex when files and pages are
visited by easy_install
- a virtualenv-compatible version, so the next virtualenv release will
be able to provide a --distribute option.
You can visit http://pypi.python.org/pypi/distribute#id2 for a full
We are now starting the 0.6.8 work in parallel of 0.7.x development,
with more bugfixes coming up.