-
-
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
__spec__ is None inside 'coverage run -m' #838
Comments
Thanks. Do you know anything about how to set it properly? Maybe now is the time to switch to using runpy in the stdlib? |
I don't know any particulars on FWIW, I do see
Per the manual:
Discussion there around PEP 451 suggests the spec handling may only be correct post Python 3.4. I've not tested anything in this manner. |
Fixed in 47d1659 |
Thank you. |
This was released as part of 5.0b2 today. |
Describe the bug
Unlike
python -m
, insidecoverage run -m
it turns out__spec__
is unexpectedlyNone
.To Reproduce
The text was updated successfully, but these errors were encountered: