delta/python-setuptools-bitbucket.git/setuptools/cli.exe, branch single-codebase bitbucket.org: Obsolete (use python-setuptools-git) issue #376: copying cli-32.exe to cli.exe and gui-32.exe to gui.exe to prevent breakage of other modules that take the binaries from distribute 2013-05-13T12:21:51+00:00 guy guy@guyr-air.infinidat.com 2013-05-13T12:21:51+00:00 6a7a27fd90efcc27d768d99f3172a932acf0dfed 






Removing legacy word-size-agnostic launchers.
2013-05-09T14:24:43+00:00

Jason R. Coombs
jaraco@jaraco.com

2013-05-09T14:24:43+00:00

a0be1d7bd2db1da67894ba8f5683a1c5fc2b16bd












Issue #207: updated executables for 32bit and 64bit
2011-09-17T13:24:50+00:00

guyroz
devnull@localhost

2011-09-17T13:24:50+00:00

923d7c0294fdd3aab8a2e659da8e531d9c6f7f75












Reversing patch for 64-bit Windows script launcher, applied PJE's simpler solution instead
2009-10-19T22:37:01+00:00

agronholm
devnull@localhost

2009-10-19T22:37:01+00:00

7285f40da8eabc9482ae9360400c1d434df678f8












Fix script launcher creation on 64-bit Windows, patch by Jason R. Coombs (http://bugs.python.org/setuptools/issue2)
2009-09-25T19:01:27+00:00

agronholm
devnull@localhost

2009-09-25T19:01:27+00:00

6970c436dada5e70b212e534560422d65e0e63c1












Fix ``#!`` parsing problems in Windows ``.exe`` script wrappers, when there
2007-01-24T21:00:55+00:00

PJ Eby
distutils-sig@python.org

2007-01-24T21:00:55+00:00

7636744224d5c47326379eaac30b9eedef1ba98a

was whitespace inside a quoted argument or at the end of the ``#!`` line
(backport from trunk)





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.
2006-12-29T17:43:39+00:00

PJ Eby
distutils-sig@python.org

2006-12-29T17:43:39+00:00

39063f8ef647375681b542376070d98347705582

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)





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 to
2006-08-22T19:58:05+00:00

Jim Fulton
distutils-sig@python.org

2006-08-22T19:58:05+00:00

b23554f2817aae43b07359552b317956561813f7

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.





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 avoid
2005-11-17T03:01:33+00:00

PJ Eby
distutils-sig@python.org

2005-11-17T03:01:33+00:00

0c4fd22a1736c2e6a17744f0bed1be55997415c3

problems when Python (or a script) is installed in a directory
whose name contains spaces.  :(





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,
2005-10-16T20:45:30+00:00

PJ Eby
distutils-sig@python.org

2005-10-16T20:45:30+00:00

78a680c55cab1f7258f120c27fd0bcfe21625751

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.





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.