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
-m broken in trunk #46096
Comments
As of today, the -m option doesn't appear to work any more in the trunk. $ ./python -m string
Could not import runpy module
$ However it seems to be confused: $ ./python -c 'import runpy'
$ IOW the module imports just fine. Crys, I wonder if this has to do with your import-nolock changes? |
Seems to work here... |
Bah. Environment error. Sorry! |
Sorry, I accidentally referenced this BPO issue in my commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: