path issue with -m doctest

[nedbat]

Originally reported by James Tauber (Bitbucket: jtauber, GitHub: jtauber)

---

I have a doctest in a separate .rst that I am able to run with

python -m doctest -v foo.rst

(where foo.rst includes an import foo in it and foo.py is alongside foo.rst in the directory).

However, when I attempt

coverage run -m doctest -v foo.rst

the tests all fail (and no coverage data is collected) because doctest is unable to import foo.

---

• Bitbucket: https://bitbucket.org/ned/coveragepy/issue/256

[nedbat]

Original comment by James Tauber (Bitbucket: jtauber, GitHub: jtauber)

---

I'm investigating this myself but wanted to log the bug in case someone beat me to it.

[nedbat]

Original comment by James Tauber (Bitbucket: jtauber, GitHub: jtauber)

---

If foo.rst has something like

>>> import sys
>>> sys.path

we can see that the issue is (as one might have guessed) that when run with python, sys.path has '' whereas when run with coverage run, sys.path does not.

[nedbat]

Original comment by James Tauber (Bitbucket: jtauber, GitHub: jtauber)

---

Possibly relevant: if I create a bar.py that prints sys.path then python bar.py does not include '' in the path but python -m bar does.

So it is as if coverage run -m is not following the python -m behaviour of adding the current directory to the path.

[nedbat]

Original comment by James Tauber (Bitbucket: jtauber, GitHub: jtauber)

---

My current workaround is to create a file:

import doctest
import sys

doctest.testfile(sys.argv[1], verbose=True)

and have coverage run that file (with the testfile passed in)