I'm looking at PyPi as infrastructure and upstream source for Linux distributions.
* Renaming packages I would strongly say NO to this one. Once you make a release, don't change it. If mistake in metadata/packaging was done, make new release like 1.0 -> 1.0-r1 * Source code requirement This one really depends on the main purpose of PyPi. If it's only there as provider of metadata garbage, then no rules should be applied. If it's main goal is to provide downloadable package companied with metadata, then source could be an requirement. Companies using PyPi as index of metadata, that's nonsense. They can setup their own pypi mirror and that would even be a more proper way. My 2 cents, Domen
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Catalog-SIG mailing list Catalog-SIG@python.org http://mail.python.org/mailman/listinfo/catalog-sig
