On Thu, Jan 28, 2016 at 11:03 PM, Charles R Harris < charlesr.har...@gmail.com> wrote:
> > > On Thu, Jan 28, 2016 at 2:36 PM, Nathaniel Smith <n...@pobox.com> wrote: > >> Maybe we should upload to pypi? This allows us to upload binaries for osx >> at least, and in general will make the beta available to anyone who does >> 'pip install --pre numpy'. (But not regular 'pip install numpy', because >> pip is clever enough to recognize that this is a prerelease and should not >> be used by default.) >> >> (For bonus points, start a campaign to convince everyone to add --pre to >> their ci setups, so that merely uploading a prerelease will ensure that it >> starts getting tested automatically.) >> On Jan 28, 2016 12:51 PM, "Charles R Harris" <charlesr.har...@gmail.com> >> wrote: >> >>> Hi All, >>> >>> I hope I am pleased to announce the Numpy 1.11.0b2 release. The first >>> beta was a damp squib due to missing files in the released source files, >>> this release fixes that. The new source filese may be downloaded from >>> sourceforge, no binaries will be released until the mingw tool chain >>> problems are sorted. >>> >>> Please test and report any problem. >>> >> > So what happens if I use twine to upload a beta? Mind, I'd give it a try > if pypi weren't an irreversible machine of doom. > One of the things that will probably happen but needs to be avoided is that 1.11b2 becomes the visible release at https://pypi.python.org/pypi/numpy. By default I think the status of all releases but the last uploaded one (or highest version number?) is set to hidden. Other ways that users can get a pre-release by accident are: - they have pip <1.4 (released in July 2013) - other packages have a requirement on numpy with a prerelease version (see https://pip.pypa.io/en/stable/reference/pip_install/#pre-release-versions) Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
