[Catalog-sig] Can PyPI have a new field that stores the code repository URL?
pydanny at gmail.com
Fri Apr 8 19:24:49 CEST 2011
In PEP-345 there isn't a specific URL field. Instead we have to hope
that people add something and then follow a 'source code' label
convention. To know to add this field, one needs to know the
convention, and that is in PEP-345, far from PyPI and its
instructions. Even if instructed, from a sociological point of view
one could argue that this is not the most efficient way to handle the
My request is for a obvious, specific field. An obvious, specific
field will encourage package owners to provide links to their source
code repositories. The field and the APIs it will feed will allow
tools like Packaginator, Read the Docs, Depot.io, and other
yet-to-be-invented tools a clear path to the source code repo for
existing and unknown reasons.
On Fri, Apr 8, 2011 at 10:09 AM, Tarek Ziadé <ziade.tarek at gmail.com> wrote:
> I added in PEP 345 a field where you can store any number of urls for
> the project
> Check it out, PyPI also support displaying it under a "Project Links" portlet
> example: http://pypi.python.org/pypi/gfbi_core/0.2
> On Fri, Apr 8, 2011 at 10:01 AM, Daniel Greenfeld <pydanny at gmail.com> wrote:
>> Projects have home pages, they also have Repos but that is not on
>> PyPI. For the forthcoming Python Packages
>> (https://github.com/cartwheelweb/packaginator) having this field would
>> mean gathering metrics on those projects would be great. Otherwise we
>> have to check 10K+ records. I know that the data will be entered in
>> eventually, but eventually we'll have the canonical repo source for a
>> greater majority of projects..
>> 'Knowledge is Power'
>> Daniel Greenfeld
>> Catalog-SIG mailing list
>> Catalog-SIG at python.org
> Tarek Ziadé | http://ziade.org
'Knowledge is Power'
More information about the Catalog-SIG