[Catalog-sig] start on static generation, and caching - apache config.

"Martin v. Löwis" martin at v.loewis.de
Wed Jul 11 22:15:44 CEST 2007

> Let's suppose that setuptools was changed to be aware that PyPI release
> pages correspond to a particular version.  In that case, it would have
> to read the package page to discover the release pages and then it would
> have to read at least one release page.  If it had requirements other
> than the version (e.g. Python version or platform), it might have to
> scan several releases to find an acceptable distribution.  But, in the
> best case, it would have to scan at least two pages.

Sure. However, that makes the difference between O(1) and O(N),
where N is the number of releases recorded. Going back to your
original concern: you would not have to change the policy of
keeping many different releases if the number of releases
does not impact performance.

When it looks for individual release pages, does it know that these
are release pages, or does it follow all links on the package
page? If the latter, what links does it follow (there are plenty
more on the package page)?


More information about the Catalog-SIG mailing list