Re: [Zope-dev] docs.zope.org automation
-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- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxXuq0ACgkQRAx5nvEhZLKuOwCeKf/h1Sb9oxUoTPOBgexPafRC essAoLISBbIoU+fQhzk9w4syHZVtKbxw =trcX -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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 path the package is >> in, not sure). > > The issue, just like with pkginfo.Develop, is that I can't find any > function or method that finds package information in subfolders. If you > look at... > > http://packages.python.org/distribute/pkg_resources.html#getting-or-creating-distributions > > ...there's this function find_distributions which supposedly offers > subfolder searching, but it just doesn't work. At least it doesn't do > what I would expect when I read the documentation. It finds nothing. 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 checkouts: http://packages.python.org/pkginfo/distributions.html#introspecting-development-checkouts Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkxXRIgACgkQ+gerLs4ltQ4n+QCdFy+tKu+Gjsi0qqNd+fwdEa5K pIkAn1uef9EUaOCib+xKI5UWcJPytKLD =4+bj -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 > > path (whether that's the path of the package or the path the package is > > in, not sure). > > The issue, just like with pkginfo.Develop, is that I can't find any > function or method that finds package information in subfolders. If you > look at... > > http://packages.python.org/distribute/pkg_resources.html#getting-or-creating-distributions > > ...there's this function find_distributions which supposedly offers > subfolder searching, but it just doesn't work. At least it doesn't do > what I would expect when I read the documentation. It finds nothing. 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. > jens > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.8 (Darwin) > > iEYEARECAAYFAkxW840ACgkQRAx5nvEhZLK0MgCfWNsSL47dimbU9TlIZNSRq07h > HLIAoIYYLdYUsA5PhYrtqhu9EaVk8Nip > =GbbC > -END PGP SIGNATURE- > ___ > Zope-Dev maillist - Zope-Dev@zope.org > https://mail.zope.org/mailman/listinfo/zope-dev > ** No cross posts or HTML encoding! ** > (Related lists - > https://mail.zope.org/mailman/listinfo/zope-announce > https://mail.zope.org/mailman/listinfo/zope ) -- Brian Sutherland ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 path of the package or the path the package is >> in, not sure). > > The issue, just like with pkginfo.Develop, is that I can't find any > function or method that finds package information in subfolders. If you > look at... > > http://packages.python.org/distribute/pkg_resources.html#getting-or-creating-distributions > > ...there's this function find_distributions which supposedly offers > subfolder searching, but it just doesn't work. At least it doesn't do > what I would expect when I read the documentation. It finds nothing. Yeah, unfortunately this is generally the point where I find myself being lost too. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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 > in, not sure). The issue, just like with pkginfo.Develop, is that I can't find any function or method that finds package information in subfolders. If you look at... http://packages.python.org/distribute/pkg_resources.html#getting-or-creating-distributions ...there's this function find_distributions which supposedly offers subfolder searching, but it just doesn't work. At least it doesn't do what I would expect when I read the documentation. It finds nothing. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW840ACgkQRAx5nvEhZLK0MgCfWNsSL47dimbU9TlIZNSRq07h HLIAoIYYLdYUsA5PhYrtqhu9EaVk8Nip =GbbC -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 scared because I always get lost. :)
The pkg_resources documentation is here:
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
in, not sure).
Then maybe 'get_metadata('long_description') on the distribution object,
but maybe not as one seems to have to supply metadata when constructing
a distribution..
But again, I always get lost here, perhaps you need an Environment or a
WorkingSet first, etc.
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 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 are proper ReST. ;-) > > I hereby declare that verifying proper ReST is OUT OF SCOPE for > docs.zope.org ;-) It's out of scope for PyPI too, what it does is just display the plain text if there are any ReST errors. And when the developer sees that, that's a clue to go and fix the ReST and use the above technique. So as long as there's a clue that "it's not working" we'll be fine. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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 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. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW41sACgkQRAx5nvEhZLIrzgCeMVQhPaa0QwSZriPxyzTkyApk 6kIAoIbmZ19Rhq4nKOksK5byw5FAwsyg =d3W2 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Class advisors in Python 3
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 for Python 2.4. I don't remember anyone speaking up to support Python 2.5 and syntactically there is little between 2.4 and 2.5. Moving the baseline to 2.6 will allow the smooth introduction of exactly such Python 3 compatability. But, at the end of the day, the decision is with the ZTK group. Charlie -- Charlie Clark Managing Director Clark Consulting & Research German Office Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Developer meeting 2010-08-02 at 15:00 UTC
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 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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*, even if it's just a page with a few words on it. > > Just FYI: If there is no long description (which is very unlikely), then the > string "UNKNOWN" is returned from the --long-description call. OK, that's an excellent flag to give up and say "this package has no documentation I can deal with". jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW3gEACgkQRAx5nvEhZLKfJwCfVC1ogbRfnzAXX7UUz8mTDYIq 4W8An25biGvShwZrZXUdFCZdFKVg+GsU =cGph -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 description (which is very unlikely), then the string "UNKNOWN" is returned from the --long-description call. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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. > > Oh, btw, this is also the method that we used to verify that the long > descriptions are proper ReST. ;-) I hereby declare that verifying proper ReST is OUT OF SCOPE for docs.zope.org ;-) jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW2/QACgkQRAx5nvEhZLJHTQCfW3YchH6YZyJA+JlDgV6J6W7j /1cAn14kcIGJLoIm5iF2KBgiou4t4YCt =0JKd -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 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 >> >> 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... > > z3c.form, I'd guess. :) Doesn't z3c.form have sphinx documentation? Wichert. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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 output from that? If it's ReST I'd have to find a way to >> convert it to HTML on the fly... > > zope.security (http://pypi.python.org/pypi/zope.security) > > Once you have docutils installed, you can do: > > py26 setup.py --long-description | rst2html > > rst2html have many options that allow you to modify the style, including the > ability to specify a stylesheet. 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. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW26cACgkQRAx5nvEhZLIczgCfamZ/m01aQt3+h7DnQTDXYpUl /3cAn2Ji0K7MQWHNWZFT/QoBENKZ/r3J =HFeU -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Developer meeting 2010-08-02 at 15:00 UTC
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.zope.org/zopetoolkit/zope-dev/zope-dev-20100803.html Christian -- 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 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 are proper ReST. ;-) Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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... zope.security (http://pypi.python.org/pypi/zope.security) Once you have docutils installed, you can do: py26 setup.py --long-description | rst2html rst2html have many options that allow you to modify the style, including the ability to specify a stylesheet. Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 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 > > 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... z3c.form, I'd guess. :) For other examples, look at e.g. z3c.caching, plone.caching or plone.testing. You can do: $ python setup.py --long-description | rst2html.py > doc.html to create an HTML file. Martin ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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 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 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... jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxW2OoACgkQRAx5nvEhZLLLlwCeKw5Y6x9r3x+WaOb1YMlJtY2j nUIAniBuzDN0MJNKbpXf6y14e+AR/sU7 =8yM8 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
-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 good to use the long > description of the package, if the other two methods fail. This would turn on > documentation for a lot of packages and we can move them over slowly. I'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. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxWzlMACgkQRAx5nvEhZLJbtgCfQXs8pT87JAVFFzRwoSKnZ4pm QuYAoJ09ArtylS+MUsYXXqmwxo/0Vogr =WBJO -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 documented using > "z3c.recipe.sphinxdoc" maintained in a separate buildout, but I'm hoping > those project authors would consider using the standard layout as > exemplified by e.g. zope.event[2] and championed by e.g. Tres, Christian > Theune, and several others (including me). 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 good to use the long description of the package, if the other two methods fail. This would turn on documentation for a lot of packages and we can move them over slowly. But otherwise, it is great to see such great progress on docs.zope.org! Regards, Stephan -- Entrepreneur and Software Geek Google me. "Zope Stephan Richter" ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 75 OK, 15 Failed, 1 Unknown
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 32bit > From: ccomb at free.fr > Date: Sun Aug 1 23:51:40 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017767.html > > Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit > From: ccomb at free.fr > Date: Sun Aug 1 23:52:18 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017768.html Changes in zope.testing requires adding zope.testrunner to the KGS, and it's not possible while there is no 1.0 branch. Instead of having a failure every day, I will run this test once a week. Anyway, people can manually trigger the builders at any time. > > Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux > From: ccomb at free.fr > Date: Mon Aug 2 01:28:17 EDT 2010 > URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017772.html This one looks like a timeout. I've raised it to 3600s. > ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope Tests: 75 OK, 15 Failed, 1 Unknown
-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 from buildbot at pov.lt, 13 from buildbot at > winbot.zope.org, 11 from ccomb at free.fr, 56 from jdriessen at > thehealthagency.com. I have a feeling these buildbots are getting out of control. Specifically, I think it's perfectly sufficient to run each buildbot just once a day instead of once per each check-in, as seems to be the case for at least the ones at thehealthagency.com. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxWtE4ACgkQRAx5nvEhZLK0EgCeLxN3vH95BNXMxHJtAGoXKTLI dk0An0EAc5aVva7HaO/lqhdZ33bW5WME =4zq6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 75 OK, 15 Failed, 1 Unknown
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 jdriessen at thehealthagency.com. Test failures - Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Sun Aug 1 08:52:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017699.html Subject: FAILED : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Aug 1 19:52:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017742.html Subject: FAILED : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Aug 1 19:52:52 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017743.html Subject: FAILED : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Sun Aug 1 19:52:53 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017744.html Subject: FAILED : winbot / ztk_dev py_244_win32 From: buildbot at winbot.zope.org Date: Sun Aug 1 22:08:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017756.html Subject: FAILED : winbot / ztk_dev py_254_win32 From: buildbot at winbot.zope.org Date: Sun Aug 1 22:15:19 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017758.html Subject: FAILED : winbot / ztk_dev py_265_win32 From: buildbot at winbot.zope.org Date: Sun Aug 1 22:21:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017759.html Subject: FAILED : winbot / ztk_dev py_265_win64 From: buildbot at winbot.zope.org Date: Sun Aug 1 22:28:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017760.html Subject: FAILED : winbot / ztk_10 py_254_win32 From: buildbot at winbot.zope.org Date: Sun Aug 1 22:44:44 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017763.html 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 32bit From: ccomb at free.fr Date: Sun Aug 1 23:51:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017767.html Subject: FAILED : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Sun Aug 1 23:52:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017768.html Subject: FAILED : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Mon Aug 2 01:28:17 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017772.html Subject: FAILED : winbot / ZODB_dev py_270_win32 From: buildbot at winbot.zope.org Date: Mon Aug 2 03:12:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/01.html Subject: FAILED : winbot / ZODB_dev py_270_win64 From: buildbot at winbot.zope.org Date: Mon Aug 2 04:07:45 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017779.html Unknown --- Subject: [zodb-tests] buildbot failure in Enfold Systems on zodb-trunk-python-2.6-maestro From: buildbot at enfoldsystems.com Date: Mon Aug 2 04:06:03 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017778.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Aug 1 08:54:40 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017700.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Aug 1 08:54:49 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017701.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Aug 1 09:32:19 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017702.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Aug 1 09:33:31 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017703.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Aug 1 09:34:11 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017704.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Sun Aug 1 09:35:48 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017705.html Subject: OK : Zope Buildbot / ztk slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Sun Aug 1 09:39:26 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-August/017706.html Subject: OK : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Sun Aug 1 09:4
Re: [Zope-dev] docs.zope.org automation
-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 expose its documentation > separately from project foo. Perhaps "Zope" would be a good example. :) The specific desire was to offer URLs http://docs.zope.org/, that's why I created it that way. It's not that hard to add a subdirectory, but I'd rather have consensus first. Me personally I like the straight package URLs without an intermediary subfolder. > P.S. It'd be good if the ZODB section had at least a link to zodb.org. > Links to buildout.org and grok.zope.org might also be useful. Take a look at the "Related Links" on the left hand side, they're all in there except for grok.zope.org, which I just added. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkxWsOQACgkQRAx5nvEhZLKZOgCdGGocKi8dFHkAXPP7W1a7Bqn0 0ZcAnRROfJWNE7ET1ngivR2gvnnb8BYC =X2Io -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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 >> docs.zope.org, e.g.: >> >> 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 expose its documentation > separately from project foo. Perhaps "Zope" would be a good example. :) Perhaps we should encourage people to upload documentation to packages.python.org ? Wichert. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] docs.zope.org automation
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.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 expose its documentation separately from project foo. Perhaps "Zope" would be a good example. :) Regards, Martijn P.S. It'd be good if the ZODB section had at least a link to zodb.org. Links to buildout.org and grok.zope.org might also be useful. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
