This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients Viv, brett.cannon, eric.snow, eryksun, jwilk, ncoghlan, ned.deily, njs, ztane
Date 2018-03-25.10:54:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1521975243.23.0.467229070634.issue33053@psf.upfronthosting.co.za>
In-reply-to
Content
PR posted with the change to use an absolute path for the starting working directory in the "-m" case.

That PR also includes a change to improve the fidelity of the test suite: back when I first wrote test_cmd_line_script, I was mainly focused on testing the runpy aspects, and not the sys.path initialisation aspects, so the way the tests worked didn't really check the latter properly.

The test updates get rid of the launch script that was previously confusing matters, and instead test sys.path[0] initialisation properly (relying on `PYTHONPATH` for the zipimport related cases where just changing the working directory isn't sufficient).
History
Date User Action Args
2018-03-25 10:54:03ncoghlansetrecipients: + ncoghlan, brett.cannon, jwilk, ned.deily, njs, eric.snow, eryksun, ztane, Viv
2018-03-25 10:54:03ncoghlansetmessageid: <1521975243.23.0.467229070634.issue33053@psf.upfronthosting.co.za>
2018-03-25 10:54:03ncoghlanlinkissue33053 messages
2018-03-25 10:54:02ncoghlancreate