delta/python-setuptools-git.git - github.com: pypa/setuptools.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Quote arguments to python.exe (including python's path) to avoid	PJ Eby	2005-11-17	1	-10/+10
\| \| \| \| \| \| \| \| \|	problems when Python (or a script) is installed in a directory whose name contains spaces. :( --HG-- branch : setuptools extra : convert_revision : svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/sandbox/trunk/setuptools%4041460
*	Fix problem with Windows console scripts conflicting with module names,	PJ Eby	2005-10-16	1	-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. --HG-- branch : setuptools extra : convert_revision : svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/sandbox/trunk/setuptools%4041261
*	Support generating .pyw/.exe wrappers for Windows GUI scripts, and	PJ Eby	2005-09-24	1	-14/+14
\| \| \| \| \| \| \| \|	"normal" #! wrappers for GUI scripts on other platforms. --HG-- branch : setuptools extra : convert_revision : svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/sandbox/trunk/setuptools%4041254
*	Added support to solve the infamous "we want .py on Windows, no	PJ Eby	2005-09-17	1	-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. --HG-- branch : setuptools extra : convert_revision : svn%3A6015fed2-1504-0410-9fe1-9d1591cc4771/sandbox/trunk/setuptools%4041246