On Fri, Dec 18, 2009 at 9:56 AM, Darren Dale <[email protected]> wrote: > On Fri, Dec 18, 2009 at 9:41 AM, Tarek Ziadé <[email protected]> wrote: >> Hi, >> >> While PEP 386 is waiting to be accepted in python-dev, I'd like to >> finish PEP 345 so we can propose it right after PEP 386 is (hopefully) >> accepted. >> >> The remaining point I can see is about : Repository-URL, >> Repository-Browse-URL, Bug-Tracker-URL. >> >> As Ian suggested I propose to change these three fields to: >> >> Project-URL (multiple-use) : >> >> A string containing an URL for the project and a label for it. >> separated by a comma >> >> Example:: >> >> Bug Tracker, http://bitbucket.org/tarek/distribute/issues/ >> >> >> This field, like Requires-Dist, can be present multiple times. The >> label of the URL is preferrably unique >> but there will be no control of this unicity. Although the label is >> limited to 32 signs so the developer stay concise. >> The URL is a valid browsable URL. (http/ftp/https). >> >> PyPI could then use these URLs on the project page like this: >> >> <a href="http://bitbucket.org/tarek/distribute/issues/";>Bug Tracker</a> >> >> >> Any thoughts ? > > I have a question about fields being present multiple times. Should > the format be compatible with ConfigParser? I don't think ConfigParser > knows how to handle this situation.
Sorry, I think I confused this with declaring metadata in setup.cfg (PEP 390). Darren _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
