On Thu, Aug 05, 2010 at 08:35:20AM +0200, Jens Vagelpohl wrote:
> On 8/5/10 00:16 , Willi Langenberger wrote:
> > According to Jens Vagelpohl:
> >> before=$(svn info $ROOT | grep "^Last Changed Rev:" | cut -d " " -f 4)
> >> svn up -q $ROOT
> >> after=$(svn info $ROOT | grep "^Last Changed Rev:" | c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/5/10 00:16 , Willi Langenberger wrote:
> According to Jens Vagelpohl:
>> before=$(svn info $ROOT | grep "^Last Changed Rev:" | cut -d " " -f 4)
>> svn up -q $ROOT
>> after=$(svn info $ROOT | grep "^Last Changed Rev:" | cut -d " " -f 4)
>
> I thin
On Wed, Aug 04, 2010 at 05:41:08PM +0200, Wichert Akkerman wrote:
> On 8/4/10 17:38 , Jens Vagelpohl wrote:
> > IMHO trying to come up with some kind of programmatic algorithm to judge
> > a bit of documentation as "good enough to show" is insane. I'm not
> > going to attempt it.
>
> Fair enough.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 17:41 , Wichert Akkerman wrote:
> On 8/4/10 17:38 , Jens Vagelpohl wrote:
>> Maybe "shitty" (for some definition of "shitty", as someone else would
>> say) package docs will compel the maintainers to improve them.
>
> I doubt it, considering
On 8/4/10 17:38 , Jens Vagelpohl wrote:
> IMHO trying to come up with some kind of programmatic algorithm to judge
> a bit of documentation as "good enough to show" is insane. I'm not
> going to attempt it.
Fair enough.
> Maybe "shitty" (for some definition of "shitty", as someone else would
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 17:26 , Wichert Akkerman wrote:
> I'm wondering: can it be made to skip useless docs such as
> http://docs.zope.org/zope.hookable/index.html, perhaps by checking for
> linecount?
>
> There are also a lot of packages that only have a change
On 8/4/10 16:29 , Jens Vagelpohl wrote:
> The script (see below) sits at the root of the documentation buildout
> (such as the buildout at http://svn.zope.org/zopetoolkit/), which
> precreates the necessary sphinx-build script (that's why I am modifying
> $PATH). It's run every 15 minutes to detect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 14:55 , Marius Gedminas wrote:
> On Wed, Aug 04, 2010 at 11:09:58AM +0200, Jens Vagelpohl wrote:
>> On 8/4/10 10:57 , Adam GROSZER wrote:
>>> Hello Jens,
>>>
>>> Something is wrong with the automatic update of
>>> http://docs.zope.org/zop
On Wed, Aug 04, 2010 at 11:09:58AM +0200, Jens Vagelpohl wrote:
> On 8/4/10 10:57 , Adam GROSZER wrote:
> > Hello Jens,
> >
> > Something is wrong with the automatic update of
> > http://docs.zope.org/zopetoolkit/
> >
> > Recent changes don't seem to show up.
>
> I rebuilt it now. There's
-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:
>>
>>
>> Yikes. Maybe the subshell isn't so bad after all :-P
>
>
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:
>
>
> Yikes. Maybe the subshell isn't so bad after all :-P
Yeah ;-) Although getting the right python path set up can be a pain...
Here's the actual versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/4/10 10:57 , Adam GROSZER wrote:
> Hello Jens,
>
> Something is wrong with the automatic update of
> http://docs.zope.org/zopetoolkit/
>
> Recent changes don't seem to show up.
I rebuilt it now. There's a check in a shell script to see if
Hello Jens,
Something is wrong with the automatic update of
http://docs.zope.org/zopetoolkit/
Recent changes don't seem to show up.
--
Best regards,
Adam GROSZER mailto:agros...@gmail.com
--
Quote of the day:
For happiness one needs security, but joy can spring l
-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:
Yikes. Maybe the subshell isn't so bad after all :-P
jens
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
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 setupto
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 Tue, Aug 3, 2010 at 11:05 PM, 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 importin
-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 h
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 m
-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 g
-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 chec
-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
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
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
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 tha
-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 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
On 08/02/2010 04:53 PM, Jens Vagelpohl wrote:
> -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 mod
-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 fu
-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 *somet
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 descri
-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 sty
On 8/2/10 16:46 , Martin Aspeli wrote:
> On 2 August 2010 22:40, Jens Vagelpohl 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 documentatio
-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 t
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
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 2 August 2010 22:40, Jens Vagelpohl 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 introspection on
-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 fu
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
-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 g
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
-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 w
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 unde
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.:
>
> http://docs.z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
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.:
http://doc
45 matches
Mail list logo
