I want to launch with...
python.exe -u -m mypackage.mymodule
I understand I can add the -m, but how do I get it to use the proper package.module.
As of Wing 7.2, you do this with Environment under the Debug/Execute tab in File Properties, or you can set up a Named Entry Point from the Debug menu and select Named Module and enter the module name.
You can also locate runpy with at any python prompt:
import runpy
print(runpy.__file__)
@gadgersteve, I just want to check with you that this continues to be true for virtual environments.
Thanks.
Some quick testing shows that runpy is not copied as a part of the virtual environment for venv nor virtualenv on 2.7 but is on the python path in all of my tests so the above gives the same result both in the virtual environments that I have tested and in normal use.- note that os is copied and gives different results in the venv to normal use so it is working fine!
The -m option is not currently supported. We plan to add support for it soon.
What is the suggested workaround? I ask because I have a large main project that I am using to evaluate Wing Pro against, and it requires the use of -m format.
====EDIT====
Let me rephrase that. I know of no other way to run it w/o the -m option. I am open to being schooled.
A workaround is to use runpy.py in the standard library as the main debug file and specify the module name as the first argument -- so to debug the equivalent of python -m pip, the arguments for runpy.py would be: pip
To easily find runpy.py, add import runpy to a file and then use goto definition on runpy.
Comments