Phillip J. Eby wrote: >>- auto-generate download_urls for package uploads > > > This seems unnecessary to me, since easy_install reads the upload links > just fine where they are, but of course I'm biased. :)
It might be nice if PyPI can figure out SF download links. Then if SF changes its format again PyPI can be updated and easy_install won't have to be. It's a lot easier to update the one and only PyPI than every easy_install. >>- command-line tool to query pypi and fetch entries (is this necessary >> given easy_install?) > > > A stable, documented interface to perform the operations that easy_install > does now via screen-scraping and URL interpretation would be useful. Would that be the XML-RPC interface? > The other things I'd add to the list are (decreasing priority): > > 1) the ability to treat project names and versions as case-insensitive, > while removing extraneous characters (as in pkg_resources.safe_name()) for > purposes both of searching and determining name uniqueness when registering. I'm guessing that means: if someone goes to /pypi/foo and the real name is Foo, then redirect them to /pypi/Foo. > 2) Compute "cheesecake" scores for modified entries (using only the metrics > that don't actually run any of the package's code, of course) and display > them prominently. :) Or alternately, have a way of uploading scores (from a trusted source), and then the scores can be calculated offline on a less important server. This will make it easier to develop Cheesecake too, since it can be updated without updating PyPI. I'm guessing the Cheesecake results can be summarized by a single score and then some human-readable HTML describing the score. -- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org _______________________________________________ Catalog-sig mailing list Catalog-sig@python.org http://mail.python.org/mailman/listinfo/catalog-sig
