| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
prevent breakage of other modules that take the binaries from distribute
|
| | |
|
| | |
|
| |
|
|
| |
solution instead
|
| |
|
|
| |
(http://bugs.python.org/setuptools/issue2)
|
| |
|
|
|
| |
was whitespace inside a quoted argument or at the end of the ``#!`` line
(backport from trunk)
|
| |
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
problems when Python (or a script) is installed in a directory
whose name contains spaces. :(
|
| |
|
|
|
|
|
| |
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.
|
|
|
"normal" #! wrappers for GUI scripts on other platforms.
|
