Message335705
Folks use "python -m myproject.mymodule" to run code that they're working on all the time - it's currently the only way to get sys.path right for cases like that (otherwise you're exposed to the double import trap, where you can get two copies of a submodule under different names).
We even use it to run CPython's own test suite as "./python -m test".
That said, over in https://bugs.python.org/issue33053#msg314192 I came up with a plausible migration path away from doing that implicitly - we'd just have to introduce a spelling for doing it explicitly instead, and relative imports give us a precedent for that. |
|
Date |
User |
Action |
Args |
2019-02-16 17:47:39 | ncoghlan | set | recipients:
+ ncoghlan, ronaldoussoren, vstinner, eric.snow, Gabriel Corona, xtreak |
2019-02-16 17:47:39 | ncoghlan | set | messageid: <1550339259.7.0.667623393192.issue35971@roundup.psfhosted.org> |
2019-02-16 17:47:39 | ncoghlan | link | issue35971 messages |
2019-02-16 17:47:39 | ncoghlan | create | |
|