<div><span style="color: rgb(160, 160, 168); ">On Tuesday, February 7, 2012 at 12:02 PM, PJ Eby wrote:</span></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On Mon, Feb 6, 2012 at 3:17 PM, Andreas Jung <span dir="ltr"><<a href="mailto:lists@zopyx.com">lists@zopyx.com</a>></span> wrote:<br><blockquote type="cite"><div>
<div>My point about this: if a person does not want</div>
to host its package on PyPi than it should stay away from PyPI. Package<br>
hygiene and a certain level of professional package repository is more<br>
important and personal reasons for not hosting packages on PyPI.<br></div></blockquote><div><br></div><div>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.'</div></div></div></div></span></blockquote><div>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. </div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;"><span><div><div><div>
<div><br></div></div>
</div><div><div>_______________________________________________</div><div>Catalog-SIG mailing list</div><div><a href="mailto:Catalog-SIG@python.org">Catalog-SIG@python.org</a></div><div><a href="http://mail.python.org/mailman/listinfo/catalog-sig">http://mail.python.org/mailman/listinfo/catalog-sig</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>