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. The order in which versions of python are run is only loosely correlated to which version of the script is installed, and file timestamps are somehow involved. j...@gnu:~/tmp/winpdb-1.4.6>dh_auto_build >/dev/null 2>&1 j...@gnu:~/tmp/winpdb-1.4.6>touch build/scripts-2.4/* j...@gnu:~/tmp/winpdb-1.4.6>dh_auto_install >/dev/null 2>&1 j...@gnu:~/tmp/winpdb-1.4.6>head -1 debian/winpdb/usr/bin/winpdb #!/usr/bin/python2.4 j...@gnu:~/tmp/winpdb-1.4.6>touch build/scripts-2.5/* j...@gnu:~/tmp/winpdb-1.4.6>dh_auto_install >/dev/null 2>&1 j...@gnu:~/tmp/winpdb-1.4.6>head -1 debian/winpdb/usr/bin/winpdb #!/usr/bin/python j...@gnu:~/tmp/winpdb-1.4.6>touch build/scripts-2.4/* j...@gnu:~/tmp/winpdb-1.4.6>dh_auto_install >/dev/null 2>&1 hej...@gnu:~/tmp/winpdb-1.4.6>head -1 debian/winpdb/usr/bin/winpdb #!/usr/bin/python2.4 -- see shy jo
signature.asc
Description: Digital signature
