remove an old issue.
This commit is contained in:
parent
1111d5b26b
commit
4c6a11b8e1
14
ISSUES.txt
14
ISSUES.txt
|
@ -88,20 +88,6 @@ appropriately to avoid this issue. Moreover/Alternatively, we could
|
||||||
record which implementations of a hook succeeded and only call their
|
record which implementations of a hook succeeded and only call their
|
||||||
teardown.
|
teardown.
|
||||||
|
|
||||||
consider and document __init__ file usage in test directories
|
|
||||||
---------------------------------------------------------------
|
|
||||||
tags: bug core
|
|
||||||
|
|
||||||
Currently, a test module is imported with its fully qualified
|
|
||||||
package path, determined by checking __init__ files upwards.
|
|
||||||
This has the side effect that a source package at the root
|
|
||||||
of the test dir could be imported as well. This is somewhat
|
|
||||||
convenient but complicates the picture for running tests against
|
|
||||||
different versions of a package. Also, implicit sys.path
|
|
||||||
manipulations are problematic per-se. Maybe factorting out
|
|
||||||
a pytest_addsyspath hook which can be disabled from the command line
|
|
||||||
makes sense. In any case documentation/recommendations for
|
|
||||||
certain scenarios makes sense.
|
|
||||||
|
|
||||||
relax requirement to have tests/testing contain an __init__
|
relax requirement to have tests/testing contain an __init__
|
||||||
----------------------------------------------------------------
|
----------------------------------------------------------------
|
||||||
|
|
Loading…
Reference in New Issue