Message193348
Glancing back, it isn't perhaps clear to the casual reader what's being proposed here, and why. The idea is that a pip-style installer become part of core Python. For Windows users, any standalone scripts from an installed package would be placed in scripts/ with a stub .exe which is a copy of the py.exe launcher which would launch the corresponding Python file.
So, for a package Foo with a run-foo script, there would be: scripts/run-foo-script.py and scripts/run-foo.exe. The latter is a copy of the PEP397 launcher which interrogates its own filename (run-foo.exe) and looks for a corresponding Python script (run-foo-script.py) and then uses the launcher mechanics to run it, making use of all the built-in shebang-handling, command-line switches, etc.
This patch allows the py.exe launcher to be used in either way, transparently, inserting the run-foo-script.py filepath as a first parameter before the rest of the code runs. |
|
Date |
User |
Action |
Args |
2013-07-19 07:53:32 | tim.golden | set | recipients:
+ tim.golden, mhammond, paul.moore, vinay.sajip, jkloth |
2013-07-19 07:53:32 | tim.golden | set | messageid: <1374220412.13.0.31999091433.issue18491@psf.upfronthosting.co.za> |
2013-07-19 07:53:32 | tim.golden | link | issue18491 messages |
2013-07-19 07:53:31 | tim.golden | create | |
|