Indeed, we do something similar in astropy, with a pre-release failure
being considered breakage (rather than ignorable as for -dev):
https://github.com/astropy/astropy/blob/master/.travis.yml#L142
-- Marten
___
NumPy-Discussion mailing list
NumPy-Discus
Hi Nathan,
One very helpful think you could do, is add a Travis-CI matrix entry
where you are testing against the latest numpy nightly builds.
I got a bit lost in your tox setup, but the basic idea is that, for
one test entry, you add the following flags to pip:
-f
https://7933911d6844c6c53a7d-
OK I guess I missed that announcement.
I wouldn’t mind more than one email with a reminder to test.
On Wed, Jun 13, 2018 at 7:42 PM Charles R Harris
wrote:
> On Wed, Jun 13, 2018 at 6:28 PM, Nathan Goldbaum
> wrote:
>
>> Hi Chuck,
>>
>> Are you planning on doing an rc release this time? I thin
On Wed, Jun 13, 2018 at 6:28 PM, Nathan Goldbaum
wrote:
> Hi Chuck,
>
> Are you planning on doing an rc release this time? I think the NumPy 1.14
> release was unusually bumpy and part of that was the lack of an rc. One
> example: importing h5py caused a warning under numpy 1.14 and an h5py
> rel
Request for a -rc seconded (although this time we should be fine for
astropy, as things are working well with -dev).
-- Marten
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
Hi Chuck,
Are you planning on doing an rc release this time? I think the NumPy 1.14
release was unusually bumpy and part of that was the lack of an rc. One
example: importing h5py caused a warning under numpy 1.14 and an h5py
release didn’t come out with a workaround or fix for a couple months. Th
