<div class="gmail_quote">On Tue, Feb 7, 2012 at 12:06 PM, Donald Stufft <span dir="ltr"><<a href="mailto:donald.stufft@gmail.com">donald.stufft@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5">
<div><span style="color:rgb(160,160,168)">On Tuesday, February 7, 2012 at 12:02 PM, PJ Eby wrote:</span></div>
</div></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div><div><div><div></div><div class="h5">On Mon, Feb 6, 2012 at 3:17 PM, Andreas Jung <span dir="ltr"><<a href="mailto:lists@zopyx.com" target="_blank">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></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. </div></blockquote><div><br></div><div>Yes, but now we get into the wonderful world of how many releases do you actually want active vs. hidden vs. deleted, and now there are that many more files to be possible frozen and mirrored and archived and whatnot, which isn't really suitable for such dev releases.</div>
<div><br></div><div>(Also, in the specific case of my snapshot-only packages, I have automated builds that keep a rotating set of snapshots in a server-local download directory for public access; I wouldn't want that build process automatically uploading that stuff to PyPI, as it adds more moving parts for things to break on my end.)</div>
<div><br></div></div>