Jens Vagelpohl wrote:
I understand that. But it must be possible to do that programatically in
my code. I mean, setup.py --long-description obviously executes Python
code, which I may be able to execute myself in my current interpreter
session by importing and executing stuff from setuptools.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chris,
I've just been doing some build and release tools for a customer that
involve this sort of stuff, I resorted to:
snip lots of code
Yikes. Maybe the subshell isn't so bad after all :-P
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 11:33 , Chris Withers wrote:
Jens Vagelpohl wrote:
I've just been doing some build and release tools for a customer that
involve this sort of stuff, I resorted to:
snip lots of code
Yikes. Maybe the subshell isn't so bad after all :-P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Brian,
Do you have access to an source distribution (tarball or zip) for the
package involved?
In the source distribution the PKG-INFO file is always at the top level.
No, these are trunk checkouts.
jens
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/10 00:19 , Tres Seaver wrote:
The 'pkginfo' utility knows how to extract package metadata from stuff
installed on the path:
http://packages.python.org/pkginfo/distributions.html#introspecting-installed-packages
as well as from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 15:51 , Stephan Richter wrote:
We have put a lot of energy into putting the full documentation of packages
into the package's long description and most packages have this layout (I
know, because I did it for most. ;-) So it might be
On Tue, Aug 03, 2010 at 10:42:42PM +0200, Jens Vagelpohl wrote:
On 8/2/10 15:51 , Stephan Richter wrote:
We have put a lot of energy into putting the full documentation of packages
into the package's long description and most packages have this layout (I
know, because I did it for most.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/10 22:59 , Marius Gedminas wrote:
On Tue, Aug 03, 2010 at 10:42:42PM +0200, Jens Vagelpohl wrote:
listing, like the ZTK list[1]. I had to resort to executing setup.py
--long-description in a subprocess, unfortunately. Never found out how
to
On Tue, Aug 3, 2010 at 11:05 PM, Jens Vagelpohl j...@dataflake.org wrote:
I understand that. But it must be possible to do that programatically in
my code. I mean, setup.py --long-description obviously executes Python
code, which I may be able to execute myself in my current interpreter
On Tuesday, August 03, 2010, Jens Vagelpohl wrote:
This is now implemented as fallback, take another look at the package
listing, like the ZTK list[1]. I had to resort to executing setup.py
--long-description in a subprocess, unfortunately. Never found out how
to do that programmatically.
On 07/31/2010 07:22 PM, Jens Vagelpohl wrote:
Here's a followup on a docs.zope.org automation task I took over during
one of the Zope developer IRC metings[1]. The task was to provide
individual package documentation, if it exists, directly underneath
docs.zope.org, e.g.:
On 8/2/10 13:40 , Martijn Faassen wrote:
On 07/31/2010 07:22 PM, Jens Vagelpohl wrote:
Here's a followup on a docs.zope.org automation task I took over during
one of the Zope developer IRC metings[1]. The task was to provide
individual package documentation, if it exists, directly underneath
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martijn,
http://docs.zope.org/zope.event/
Really cool!
Wouldn't it be good to put this under /package/zope.event to avoid
potential naming conflicts? I realize they're rare, but I can imagine
that a project foo could exist that wants to
On Saturday, July 31, 2010, Jens Vagelpohl wrote:
Currently the buildout can recognize the standard Sphinx documentation
layout with a folder named doc or docs in the package root and a
Sphinx configuration and content therein. The buildout can also use a
kludge and pull in content that is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 15:51 , Stephan Richter wrote:
We have put a lot of energy into putting the full documentation of packages
into the package's long description and most packages have this layout (I
know, because I did it for most. ;-) So it might be
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
On 2 August 2010 22:40, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
On Monday, August 02, 2010, Jens Vagelpohl wrote:
Thanks for the hint, I'll try that. Can you give me a sample package
where the long description is supposed to be the main documentation? And
what's the output from that? If it's ReST I'd have to find a way to
convert it to HTML on the fly...
On Monday, August 02, 2010, Stephan Richter wrote:
py26 setup.py --long-description | rst2html
rst2html have many options that allow you to modify the style, including
the ability to specify a stylesheet.
Oh, btw, this is also the method that we used to verify that the long
descriptions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 16:48 , Stephan Richter wrote:
On Monday, August 02, 2010, Jens Vagelpohl wrote:
Thanks for the hint, I'll try that. Can you give me a sample package
where the long description is supposed to be the main documentation? And
what's the
On 8/2/10 16:46 , Martin Aspeli wrote:
On 2 August 2010 22:40, Jens Vagelpohlj...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 16:50 , Stephan Richter wrote:
On Monday, August 02, 2010, Stephan Richter wrote:
py26 setup.py --long-description | rst2html
rst2html have many options that allow you to modify the style, including
the ability to specify a stylesheet.
On Monday, August 02, 2010, Jens Vagelpohl wrote:
OK, I'll see what I can do with that. I'll probably end up using the
long description as last fallback. So you will see every package linked
to *something*, even if it's just a page with a few words on it.
Just FYI: If there is no long
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 17:00 , Stephan Richter wrote:
On Monday, August 02, 2010, Jens Vagelpohl wrote:
OK, I'll see what I can do with that. I'll probably end up using the
long description as last fallback. So you will see every package linked
to *something*,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
On 08/02/2010 05:25 PM, Jens Vagelpohl wrote:
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?
Oh, this is where I always get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 18:26 , Martijn Faassen wrote:
http://packages.python.org/distribute/pkg_resources.html
You can probably create a Distribution object somehow (handwave) from a
path (whether that's the path of the package or the path the package is
On 08/02/2010 06:34 PM, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 18:26 , Martijn Faassen wrote:
http://packages.python.org/distribute/pkg_resources.html
You can probably create a Distribution object somehow (handwave) from a
path (whether that's the
On Mon, Aug 02, 2010 at 06:34:21PM +0200, Jens Vagelpohl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 18:26 , Martijn Faassen wrote:
http://packages.python.org/distribute/pkg_resources.html
You can probably create a Distribution object somehow (handwave) from a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
On 8/2/10 18:26 , Martijn Faassen wrote:
http://packages.python.org/distribute/pkg_resources.html
You can probably create a Distribution object somehow (handwave) from a
path (whether that's the path of the package or the
31 matches
Mail list logo
