We're revamping the web interface to match the new pdo style. We've also cleaned a bit of the interface up. Phillip J. Eby wrote: > 1. It assumes that baseURL/projectname will get to the current version > of projectname, or a page with a list of projectname's active versions > > 2. It assumes that links within PyPI of the form > baseURL/something1/something2 are links to version 'something2' of a > project named 'something1' > > 4. It assumes that if baseURL/projectname returns a page containing the > text "Index of Packages", it is a list of links of the form > described in #2. > > 5. It looks for and follows the first links following the strings > "Home Page" and "Download URL" in a project page. These remain unchanged. > 3. It assumes that going to baseURL directly will result in a page with > links to all available packages in the form described in #2. This has been removed as it seems completely unnecessary (a flat listing of all 1400+ packages, that is). The XML-RPC interface provides the functionality you require here. > Also note that even with an XML-RPC interface, easy_install will *still* > need to read an HTML page to gather links, because it's valid for people > to provide links in their long_description using reStructuredText. It's > just that assumptions 1, 3, and 4 (and maybe 5) would not be necessary. You couldn't just call release_data and parse URLs out of the description text with a simple re search? > Hm. I just tried to make multiple versions of PEAK active, and it seems > like you can't get the page that lists multiple versions any more. No > wonder some people have been having problems downloading older versions > of certain packages. :( Whoopsie. This has been fixed. Not sure when it was changed or why. > What do you mean? You can run "easy_install -u setuptools" to upgrade > to the latest release at any time. But it doesn't go out looking for > updates on its own. Automatically updating existing users to use the xml-rpc would be nice, I suppose. Richard