-----BEGIN PGP SIGNED MESSAGE-----
On 8/2/10 16:36 , Stephan Richter wrote:
> On Monday, August 02, 2010, Jens Vagelpohl wrote:
>> 'll have to look at that. Currently, the documentation builder does not
>> do any introspection on the package itself, mostly because I do not want
>> to fully install the package and pull in all dependencies. Maybe there's
>> a simple way that does not require full installation.
> I agree. This does not build the package:
> python setup.py --long-description
Can someone tell me how to do that when I am in Python code already?
Given the path to the checkout, can I use some setuptools/pkg_resources
or pkginfo magic to get at this data?
My specific problem is this: Many packages define an intermediate
folder, like "src", in which the actual code path is stored. When
someone runs "setup.py egg_info" then the .egg-info folder ends up in
"src" and not at the root. Trying to use e.g. pkginfo.Develop or
pkg_resources.find_distributions with the root folder won't find the
.egg-info folder in the "src" subfolder. I'd have to do something
horrible like os.walk to find distributions, which I really don't want.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
-----END PGP SIGNATURE-----
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -