On Tue, Jul 11, 2017 at 5:04 PM, Thomas Caswell wrote:
> Going with option 2 is probably the best option so that you can use pytest
> fixtures and parameterization.
>
I agree -- those are worth a lot!
-CHB
> Might be worth looking at how Matplotlib re-arranged things on our master
> branch t
Going with option 2 is probably the best option so that you can use pytest
fixtures and parameterization.
Might be worth looking at how Matplotlib re-arranged things on our master
branch to maintain back-compatibility with nose-specific tools that were
used by down-stream projects.
Tom
On Tue, J
On Tue, 2017-07-11 at 14:49 -0600, Charles R Harris wrote:
> Hi All,
>
> Just looking for opinions and feedback on the need to keep NumPy from
> having a hard nose/pytest dependency. The options as I see them are:
>
> pytest is never imported until the tests are run -- current practice
> with nos
Hi All,
Just looking for opinions and feedback on the need to keep NumPy from
having a hard nose/pytest dependency. The options as I see them are:
1. pytest is never imported until the tests are run -- current practice
with nose
2. pytest is never imported unless the testfiles are impor
