<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 8, 2015 at 7:26 PM, Nathaniel Smith <span dir="ltr"><<a href="mailto:njs@pobox.com" target="_blank">njs@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><p dir="ltr">On Oct 8, 2015 5:39 PM, "Charles R Harris" <<a href="mailto:charlesr.harris@gmail.com" target="_blank">charlesr.harris@gmail.com</a>> wrote:<br>
><br>
> On Thu, Oct 8, 2015 at 6:30 PM, Matthew Brett <<a href="mailto:matthew.brett@gmail.com" target="_blank">matthew.brett@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> I'm afraid I made a mistake uploading OSX wheels for numpy 1.10.0.<br>
>> Using twine to do the upload generated a new release - 1.10.0.post2 -<br>
>> containing only the wheels. I deleted that new release to avoid<br>
>> confusion, but now, when I try and upload the wheels to the 1.10.0<br>
>> pypi release via the web form, I get this error:<br>
>><br>
>> Error processing form<br>
>><br>
>> This filename has previously been used, you should use a different version.<br>
>><br>
>> Any chance of a post3 upload so I can upload some matching wheels?<br>
>><br>
>> Sorry about that,<br>
><br>
><br>
> Yeah, pipy is why we are on post2 already. Given the problem with msvc9, I think we are due for 1.10.1 in a day or two. Or, I could revert the troublesome commit and do a post3 tomorrow. Hmm... decisions, decisions. I'll see if Julian has anything to say in the morning and go from there.</p>
</span><p dir="ltr">I vote that we increment the micro number every time we upload a new source release, and reserve the postN suffix for binary-only uploads. If this means we have a tiny 1.10.1 then oh well, there's always 1.10.2 -- we probably won't run out of numbers :-).</p></blockquote><div><br></div><div>The only difference between 1.10.0 and 1.10.0.post2 is that the latter is signed. Sigh. We need to capture this experience in the HOWTO_RELEASE document. Matthew, can you take care of that?<br><br></div><div>Chuck <br></div><br></div></div></div>