Sanghyeon Seo | 1 Sep 2006 06:41
Picon

Table of Python Packages

Hello, c.l.py, and catalog-sig,

This post updates last year's post:
http://mail.python.org/pipermail/catalog-sig/2005-March/000506.html

Believe it or not, I am still maintaining this table, and it can be
now found here:
http://sparcs.kaist.ac.kr/~tinuviel/package/list.cgi?name=python

Now you can see version comparison between distributions:
http://sparcs.kaist.ac.kr/~tinuviel/package/list.cgi?name=python&version=1

Version information is updated daily by an automated cron job. Now the
table contains over 400 entries.

If you have any suggestions or corrections, please mail me.

Seo Sanghyeon
--

-- 
http://mail.python.org/mailman/listinfo/python-list

Jim Fulton | 7 Sep 2006 13:42
Gravatar

What triggers treating long descriptions text as reST in PyPI?


Most of my packages' long descriptions are treated as reST. For example:

   http://www.python.org/pypi/zc.recipe.testrunner

However, for:

   http://www.python.org/pypi/zc.recipe.egg

the long description was treated as plain text.

What triggers treatment as reStructuredText?  Is this documented  
anywhere?

Jim

--
Jim Fulton			mailto:jim <at> zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org
Richard Jones | 7 Sep 2006 14:51
Picon

Re: What triggers treating long descriptions text as reST in PyPI?

On Thursday 07 September 2006 21:42, Jim Fulton wrote:
> Most of my packages' long descriptions are treated as reST. For example:
>
>    http://www.python.org/pypi/zc.recipe.testrunner
>
> However, for:
>
>    http://www.python.org/pypi/zc.recipe.egg
>
> the long description was treated as plain text.
>
> What triggers treatment as reStructuredText?  Is this documented
> anywhere?

If the reStructuredText parsing fails for some reason it'll be treated as 
plain text. The specific docutils settings used are:

    settings_overrides={
        'raw_enabled': '0',  # no raw HTML code
        'file_insertion_enabled': '0',  # no file/URL access
        'halt_level': 2,  # at warnings or errors, raise an exception
        'report_level': 5,  # never report problems with the reST code
        }

We pass the description through the docutils trim_docstring function (from  
docutils.readers.python.moduleparser) before parsing it. This dedents as 
appropriate.

     Richard
(Continue reading)

Jim Fulton | 7 Sep 2006 15:49
Gravatar

Re: What triggers treating long descriptions text as reST in PyPI?

Yeah, Fred pointed out to me that reST barfed on my ise of the string  
"py_" in my text. :/

I should have thought to try processing the text myself.  I'll do so  
the next time I get a failure to reST.

Thanks.

Jim

On Sep 7, 2006, at 8:51 AM, Richard Jones wrote:

> On Thursday 07 September 2006 21:42, Jim Fulton wrote:
>> Most of my packages' long descriptions are treated as reST. For  
>> example:
>>
>>    http://www.python.org/pypi/zc.recipe.testrunner
>>
>> However, for:
>>
>>    http://www.python.org/pypi/zc.recipe.egg
>>
>> the long description was treated as plain text.
>>
>> What triggers treatment as reStructuredText?  Is this documented
>> anywhere?
>
> If the reStructuredText parsing fails for some reason it'll be  
> treated as
> plain text. The specific docutils settings used are:
(Continue reading)

Jim Fulton | 14 Sep 2006 13:38
Favicon

Framework classifiers


Please define the following Trove classifiers:

Framework :: Buildout

   Recipes and Extensions for zc.buildout

Framework :: ZODB

   Packages that provide objects that can be stored in the ZODB or  
packages that provide ZODB extensions, such as storage implementations.

Framework :: Zope2

   Zope 2 add-on packages.

Framework :: Zope3

   Zope3 add-on packages, especially applications.  This should be  
used for packages that are designed specifically for the Zope 3  
application server.  This classification should not be used for more  
general packages that happen to be used by or that can be used in  
Zope 3.

It sure would be nice if PyPI stored and presented classifier  
descriptions. :)

Jim
Richard Jones | 15 Sep 2006 00:32
Picon

Re: Framework classifiers

On Thursday 14 September 2006 21:38, Jim Fulton wrote:
> Please define the following Trove classifiers:
>
> Framework :: Buildout
> Framework :: ZODB
> Framework :: Zope2
> Framework :: Zope3

Done.

> It sure would be nice if PyPI stored and presented classifier
> descriptions. :)

Yeah. Perhaps a wiki page linked from the tutorial would be a good start?

    Richard
Fred Drake | 15 Sep 2006 02:18
Picon

Re: Framework classifiers

On 9/14/06, Richard Jones <richardjones <at> optushome.com.au> wrote:
> Yeah. Perhaps a wiki page linked from the tutorial would be a good start?

+1   That should be much better than the current situation.

  -Fred

--

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Every sin is the result of a collaboration." --Lucius Annaeus Seneca
Jim Fulton | 15 Sep 2006 12:52
Gravatar

Re: Framework classifiers


On Sep 14, 2006, at 6:32 PM, Richard Jones wrote:

> On Thursday 14 September 2006 21:38, Jim Fulton wrote:
>> Please define the following Trove classifiers:
>>
>> Framework :: Buildout
>> Framework :: ZODB
>> Framework :: Zope2
>> Framework :: Zope3
>
> Done.

Thanks.

>> It sure would be nice if PyPI stored and presented classifier
>> descriptions. :)
>
> Yeah. Perhaps a wiki page linked from the tutorial would be a good  
> start?

Yup.

Could it also be linked from:
http://www.python.org/pypi?%3Aaction=list_classifiers
?

Jim

--
(Continue reading)

Richard Jones | 15 Sep 2006 13:28
Picon

Re: Framework classifiers

On Friday 15 September 2006 20:52, Jim Fulton wrote:
> Could it also be linked from:
> http://www.python.org/pypi?%3Aaction=list_classifiers
> ?

I guess the problem is that that page is intended to be a plain-text listing 
of the classifiers.

    Richard
Jim Fulton | 15 Sep 2006 15:38
Gravatar

Re: Framework classifiers


On Sep 15, 2006, at 7:28 AM, Richard Jones wrote:

> On Friday 15 September 2006 20:52, Jim Fulton wrote:
>> Could it also be linked from:
>> http://www.python.org/pypi?%3Aaction=list_classifiers
>> ?
>
> I guess the problem is that that page is intended to be a plain- 
> text listing
> of the classifiers.

OK.  I assume that is because it is read by some automated processes.

Jim

--
Jim Fulton			mailto:jim <at> zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org

Gmane