[Catalog-sig] Prototype setuptools-specific PyPI index.
Phillip J. Eby
pje at telecommunity.com
Sun Jul 22 01:20:04 CEST 2007
At 12:53 AM 7/22/2007 +0200, Martin v. Löwis wrote:
> > See point #2:
> > """2. Individual project version pages' URLs must be of the form
> > base/projectname/version, where base is the package index's base URL."""
> > That's what's meant by "version pages" in point #7 -- i.e., they *must*
> > be of that two-part form for setuptools to recognize them as such.
>Ok, but I still cannot see how to fix that: there simply *is* no
>version part that I could point to.
Actually, 'version' is allowed to be an empty string, so simply
adding a trailing '/' to the links you're generating now should work.
The only thing the version part of a version page URL is used for, is
to handle links to .py files: setuptools uses the package version (if
available) to synthesize a setup.py for installing standalone .py files.
If the version is not available, it won't be able to do that, but
that's a relatively minor feature, all things considered. Few
packages are distributed via a single .py download URL, but the
package index could actually tack on an #egg designator to such links
in order to preserve 100% backward-compatibility.
>Does that mean that Jim's approach does not work?
Jim isn't providing the top-level index, and thus doesn't provide
punctuation or case corrections. The "version pages" convention is
only used by setuptools to discover additional index pages for
crawling, anyway, and his whole design is intended to prevent crawling.
> > Yes; of course, the usual rendering needs to be applied, since
> > long_description can contain reStructuredText.
>Ok, I now added these links as well.
Looks good, thanks!
More information about the Catalog-SIG