id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	launchpad_bug
149	unable to use pre-installed non-distutils-aware nevow	warner	zooko	"I just tried to upgrade the tahoebs1 testnet nodes, and got the following error:
{{{
$ allmydata-tahoe --version
Traceback (most recent call last):
  File ""/usr/bin/allmydata-tahoe"", line 5, in <module>
    from pkg_resources import load_entry_point
  File ""/usr/lib/python2.5/site-packages/pkg_resources.py"", line 2479, in <module>
    working_set.require(__requires__)
  File ""/usr/lib/python2.5/site-packages/pkg_resources.py"", line 585, in require
    needed = self.resolve(parse_requirements(requirements))
  File ""/usr/lib/python2.5/site-packages/pkg_resources.py"", line 483, in resolve
    raise DistributionNotFound(req)  # XXX put more info here
pkg_resources.DistributionNotFound: nevow>=0.6.0
}}}

On this system, nevow is installed just fine:
{{{
$ python
Python 2.5.1 (r251:54863, May  2 2007, 16:56:35) 
[GCC 4.1.2 (Ubuntu 4.1.2-0ubuntu4)] on linux2
Type ""help"", ""copyright"", ""credits"" or ""license"" for more information.
>>> import nevow
>>> nevow.__version__
'0.9.0'
>>> 
}}}

The only problem is that it wasn't installed with an .egg (or an .egg-info).
Most modern debian python packages contain .egg-info files, to let setuptools
know that the package is available, but I think this nevow package is a bit
behind the times.

Is there any way to allow perfectly usable support libraries like this get
used? Note that this checking is being done by the generated setuptools
entry-point script: the bin/allmydata-tahoe that we wrote just tries to
import and run, rather than checking for existence before importing.
"	defect	closed	critical	1.4.1	packaging	1.3.0	wontfix	debian