Re: Bug#548392: debhelper: python_distutils buildsystem and, setuptools entry_points don't use default python

[Andrew Straw <strawman@astraw.com>]

Josselin Mouette wrote:
> Le samedi 26 septembre 2009 à 17:55 -0400, Joey Hess a écrit : 
>> Andrew Straw wrote:
>>> To be sure I understand, you're saying this is a bug with setuptools,
>>> because it autogenerates the /usr/bin/my_script improperly at install
>>> time when called by "python2.4 setup.py install"?
>> No, the problem is, loosely speaking, that python is on crack.
> 
> Actually you are both right; setuptools is on crack for modifying the
> shebang, and IIRC distutils does the same.
> 

setuptools doesn't modify the shebang in the script -- it constructs the
entire script when told to, at install time, on the basis of its
entry_points declaration and the version of python actually being run
(see get_script_header() in setuptools/commands/easy_install.py ).
Therefore order-of-python-running is important for setuptools script
installation, because the last one wins. So, the default python should
run last during the install stage.

I did test and confirm that my patch as originally submitted fixes this
issue.

The winpdb issue is different I am responding directly to #547510 on that.