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
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
-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
Summary of messages to the zope-tests list.
Period Sun Aug 1 12:00:00 2010 UTC to Mon Aug 2 12:00:00 2010 UTC.
There were 91 messages: 6 from Zope Tests, 1 from buildbot at
enfoldsystems.com, 4 from buildbot at pov.lt, 13 from buildbot at
winbot.zope.org, 11 from ccomb at free.fr, 56 from jdrie
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/2/10 14:00 , Zope Tests Summarizer wrote:
> Summary of messages to the zope-tests list.
> Period Sun Aug 1 12:00:00 2010 UTC to Mon Aug 2 12:00:00 2010 UTC.
> There were 91 messages: 6 from Zope Tests, 1 from buildbot at
> enfoldsystems.com, 4
Le 02/08/2010 14:00, Zope Tests Summarizer a écrit :
> Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit
> From: ccomb at free.fr
> Date: Sun Aug 1 23:50:36 EDT 2010
> URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017766.html
>
> Subject: FAILED : ZTK 1.0dev / Python2.6.4 Linux 3
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
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 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 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 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
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
Hi everyone,
tomorrow's the weekly IRC meeting.
As Jens mentioned some progress on the documentation, I've pulled that
issue back on the Agenda for tomorrow.
Also, as Adam started documenting the wineggbuilder I've pulled the
testing/buildbot topic up.
Agenda (in a few minutes):
http://docs.z
-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 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: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 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 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 08/02/2010 04:51 PM, Christian Theune wrote:
> Hi everyone,
>
> tomorrow's the weekly IRC meeting.
That's 2010-08-03 of course ...
--
Christian Theune · c...@gocept.com
gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 0 · fax +49
Am 31.07.2010, 04:19 Uhr, schrieb Hanno Schlichting :
> Who told you that? We documented our decision at
> http://docs.zope.org/zopetoolkit/process/python-versions.html.
> Python 2.5 is nowhere close to being deprecated.
It was decided at the same time as the decision was taken to drop support
-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 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
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
-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 tha
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
-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
-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
29 matches
Mail list logo
