On Wed, Dec 23, 2009 at 23:28, Sridhar Ratnakumar <sridh...@activestate.com> wrote: > I suggested PyPI to disallow mere project listings (without sources) and > require sources to be stored in the server. One way to achieve this is > requiring package authors to use the `sdist upload` toolchain
Which only means the packages who now is not uploaded wouldn't even be listed on PyPI, which is not an improvement. > While the specific case mentioned above (metadata for a specific or the > latest version of a package) uses HTTP GET and XML, generally speaking .. to > get a) the list of recently releases, b) list of all versions of a package, > one has to use the XmlRpc API methods `changelog` and `package_releases` > respectively. Well, maybe pure http versions of those would help, but on the other hand, if you automate it, why not use xml-rpc? > As often as the mirror sites would update their content (i.e., one or more > times a day). I meant that most of the third-party apps would only need the metadata, or? I might be wrong, I haven't written any yet. :-) The automated documentation that was discussed would only need the source packages. -- Lennart Regebro: http://regebro.wordpress.com/ Python 3 Porting: http://python-incompatibility.googlecode.com/ +33 661 58 14 64 _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
