-
-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run -m cannot find module (or package) in current directory #207
Comments
Can you provide more details? I've tried but can't reproduce the problem you're reporting. Do you have a zipfile that demonstrates it? What OS and Python version are you using? |
Original comment by Antony Lee (Bitbucket: anntzer, GitHub: anntzer) Create a folder
(this error may or may not appear in a seemingly random fashion). On the other hand This is on Arch Linux with Python 2.7.3 or 3.3.0, and coverage 3.5.2. |
Re-opening while we track this down. |
BTW: the attribute error is the subject of bug #153, which is now fixed. |
Fixed in changeset fb577266b491 (bb). |
Originally reported by Antony Lee (Bitbucket: anntzer, GitHub: anntzer)
The directory from which
coverage
was started should be added at the beginning ofsys.path
(or perhaps even replace the first entry ofsys.path
, which is the directory wherecoverage
is installed), so thatcoverage run -m foo
can findfoo
in that directory (just aspython -m foo
can findfoo
in that directory).Perhaps this modification should be made temporary though (e.g. by fooling around in execfile.py).
The text was updated successfully, but these errors were encountered: