summaryrefslogtreecommitdiff
path: root/launcher.c
Commit message (Collapse)AuthorAgeFilesLines
* Added support for Windows RT (arm).Grigory Petrov2013-04-031-0/+8
|
* Issue #207: passing ctrl-c events to python child processguyroz2011-09-171-11/+91
|
* Reversing patch for 64-bit Windows script launcher, applied PJE's simpler ↵agronholm2009-10-201-16/+9
| | | | solution instead
* Fix script launcher creation on 64-bit Windows, patch by Jason R. Coombs ↵agronholm2009-09-251-3/+11
| | | | (http://bugs.python.org/setuptools/issue2)
* Backport gui.exe launcher fix.PJ Eby2008-01-031-2/+2
|
* Fix ``#!`` parsing problems in Windows ``.exe`` script wrappers, when therePJ Eby2007-01-241-4/+4
| | | | | was whitespace inside a quoted argument or at the end of the ``#!`` line (backport from trunk)
* Overhauled Windows script wrapping to support ``bdist_wininst`` better.PJ Eby2006-12-291-66/+121
| | | | | | | | Scripts installed with ``bdist_wininst`` will always use ``#!python.exe`` or ``#!pythonw.exe`` as the executable name (even when built on non-Windows platforms!), and the wrappers will look for the executable in the script's parent directory (which should find the right version of Python). (backport from trunk)
* Added quoting of script arguments and extended the quoting logic toJim Fulton2006-08-221-10/+78
| | | | | | | | | handle embedded quotes. Added support for passing a single argument on the shebang line to pass things like -O and -i. Fixed bug in handling trailing whitespace in Python command.
* Quote arguments to python.exe (including python's path) to avoidPJ Eby2005-11-171-10/+10
| | | | | problems when Python (or a script) is installed in a directory whose name contains spaces. :(
* Fix problem with Windows console scripts conflicting with module names,PJ Eby2005-10-161-4/+4
| | | | | | | thereby confusing the import process. Scripts are now generated with a suffix of the form '-script.py' to avoid conflicts. (The .exe's are still generated without the '-script' part, so you don't have to type it.) Thanks to Matthew R. Scott for reporting the problem.
* Support generating .pyw/.exe wrappers for Windows GUI scripts, andPJ Eby2005-09-241-14/+14
| | | | "normal" #! wrappers for GUI scripts on other platforms.
* Added support to solve the infamous "we want .py on Windows, noPJ Eby2005-09-171-0/+123
extension elsewhere" problem, while also bypassing the need for PATHEXT on Windows, and in fact the need to even write script files at all, for any platform. Instead, you define "entry points" in your setup script, in this case the names of the scripts you want (without extensions) and the functions that should be imported and run to implement the scripts. Setuptools will then generate platform-appropriate script files at install time, including an .exe wrapper when installing on Windows.
View Lorry Controller Status