<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 14, 2015 at 8:52 PM, Chris Barker <span dir="ltr"><<a href="mailto:chris.barker@noaa.gov" target="_blank">chris.barker@noaa.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 14, 2015 at 9:56 AM, Dave Forgac <span dir="ltr"><<a href="mailto:tylerdave@tylerdave.com" target="_blank">tylerdave@tylerdave.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">This was discussed recently here: <a href="https://github.com/pypa/packaging-problems/issues/74" target="_blank">https://github.com/pypa/packaging-problems/issues/74</a></div></blockquote><div><br></div><div>and on this list at other times. Though the above issue was pretty focused on restoring a deleted file without any changes -- which seems like a no-brainer to me, as long as someone wants to put the effort into the infrastructure.</div><div><br></div><div>(the soft delete option seems like a good idea to me).</div><div><br></div><div>But I'm talking about the cases of "whoops! I really wish I hadn't uploaded that one". We can improve the tooling (some discussion on this in this thread right now...), but people are people and some of us are stupid and/or careless. So this WILL happen.</div><div><br></div><div>And it just seems pedantic to say: hey -- you've already put that one there -- maybe even two minutes ago, so there is NO WAY to fix your mistake. If it happens quickly, then no one has downloaded it, it hasn't made its way to the mirrors, etc...</div></div></div></div></blockquote><div><br></div><div>It is not pendantic, for reasons mentioned by Donald.</div><div><br></div><div>I have not done numpy releases for half a decade now, but it was already automated enough that putting a new version was not very costly then. And you did not have travis-ci, appveyor, tox, ubiquitous AWS 5 years ago ...</div><div><br></div><div>I am sure there are things we can do to improve numpy's release process to avoid this in the future.</div><div><br></div><div>David</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>And again -- we are all adults here: if you as the package maintainer want to do somethign that is sonfusing to your users, is it up to PyPi to never let you do that? (I think it IS up to PyPi to strongly recommend that you don't -- i.e. make it hard to do, and impossible to do thoughtlessly)</div><div><br></div><div><span class="">On Wed, Oct 14, 2015 at 10:00 AM, Jeremy Stanley <span dir="ltr"><<a href="mailto:fungi@yuggoth.org" target="_blank">fungi@yuggoth.org</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""><span>> You should have to jump through all sorts of hoops, and make it<br>> really clear that it is a BAD IDEA in the general case, but it'd<br>> be good to have it be possible.<br></span></span><span class="">[...]<br><br>It used to be possible.</span></blockquote></div><div><br></div><div>Was it also easy to do without very careful consideration? Or were the hoops I mentioned in place?</div><div><br></div><div>I can't find it right now, but I think someone in this thread suggested a "staging area", so we could essentially do a trail run: upload to PyPi, tell a few trusted friends about it, have them test it, then, and only then, push it to the official channel. Maybe the infrastructure for that would be more work than it's worth, but I like it.</div><div><br></div><div>This would fit into the basic principle that you should always be able to test something in as close the final environment as possible, before you commit to it.</div><div><br></div><div>-CHB</div><div><br></div><div><br></div></div><span class="">-- <br><div><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R <a href="tel:%28206%29%20526-6959" value="+12065266959" target="_blank">(206) 526-6959</a> voice<br>7600 Sand Point Way NE <a href="tel:%28206%29%20526-6329" value="+12065266329" target="_blank">(206) 526-6329</a> fax<br>Seattle, WA 98115 <a href="tel:%28206%29%20526-6317" value="+12065266317" target="_blank">(206) 526-6317</a> main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</span></div></div>
<br>_______________________________________________<br>
Distutils-SIG maillist - <a href="mailto:Distutils-SIG@python.org">Distutils-SIG@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/distutils-sig" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/distutils-sig</a><br>
<br></blockquote></div><br></div></div>