On Tuesday, February 7, 2012 at 12:02 PM, PJ Eby wrote: > On Mon, Feb 6, 2012 at 3:17 PM, Andreas Jung <[email protected] > (mailto:[email protected])> wrote: > > My point about this: if a person does not want to host its package on PyPi > > than it should stay away from PyPI. Package > > hygiene and a certain level of professional package repository is more > > important and personal reasons for not hosting packages on PyPI. > > Note that PyPI is also used to publish metadata about packages which are in > development and only available in snapshot releases or revision control > systems. So the "it shouldn't be hosted elsewhere" argument doesn't really > wash.' This is a matter of opinion really, Personally I think if your package is in development you should publish snapshot releases to PyPI. But even then this is really a special case for packages that don't have real releases yet. For packages with real releases you can do ==dev for those. > > _______________________________________________ > Catalog-SIG mailing list > [email protected] (mailto:[email protected]) > http://mail.python.org/mailman/listinfo/catalog-sig > >
_______________________________________________ Catalog-SIG mailing list [email protected] http://mail.python.org/mailman/listinfo/catalog-sig
