>> While "current" is frowned upon[0], this is not what caused your package >> breakage. The culprit it that scripts have #!/usr/bin/pythonX.Y shebangs - >> if they were unversioned, the package would continue to work with new >> Python. > > Those are changed by python distutils, that's why a rebuild fixes the problem.
You can pass an option named --executable to the build_scripts command to override that, directly on the command line, or in a configuration file: $ cat setup.cfg [build_scripts] executable = /usr/bin/python Regards merwok (distutils2 GSoC student for PSF :) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c21fd3e.5070...@netwok.org
