[Numpy-discussion] Release vs development testing.

[Charles R Harris]

On Mon, May 13, 2019 at 11:50 AM Nathaniel Smith <njs at pobox.com> wrote:

> On Mon, May 13, 2019, 10:26 Charles R Harris <charlesr.harris at gmail.com>
> wrote:
>
>> I just checked that current wheels show the warnings when `numpy.test()`
>> is run with latest pytest.  However, moving the `pytest.ini` file into the
>> `numpy` directory is tricky, as we need to tell pytest where to find the
>> installed file (-c option). The simplest short time solution is to ignore
>> the warning, but long term I'm worried that the warning will become an
>> error as pytest is doing this because they want to clean up the their
>> implementation. Ideally there would be a better way to register the marks.
>>
>
> I bet if you open an issue on pytest explaining that numpy needs to either
> use unregistered marks or else have some programmatic non-pytest.ini-based
> way to register marks, then they'll figure something out. I think they
> added a warning because they're hoping to flush out these kinds of problems
> so they can fix them before they do the cleanup.
>
>
Turns out that markers can be registered in conftest.py, so that fixes the
problem for NumPy. SciPy will need this fix also.

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190513/a4d28561/attachment.html>