[issue14946] packaging’s pysetup script should be named differently than distutils2’s pysetup

Changes by Éric Araujo mer...@netwok.org: -- resolution: - out of date stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue14946 ___

[issue14946] packaging’s pysetup script should be named differently than distutils2’s pysetup

Alexis Metaireau ale...@notmyidea.org added the comment: Good catch, One solution would be to have the pysetup script name suffixed by the version of python is comes with. For instance, for python 3.3 it would be pysetup3.3 (that's how it is atm). This means that pysetup would point to

[issue14946] packaging’s pysetup script should be named differently than distutils2’s pysetup

Éric Araujo mer...@netwok.org added the comment: I’m afraid that won’t work: depending on how python3 is installed, it may install both pysetup3.3 and pysetup3, so distutils2-python3 can’t use any of these names. Note that on Debian and probably other systems, two packages really cannot use

[issue14946] packaging’s pysetup script should be named differently than distutils2’s pysetup

Changes by Éric Araujo mer...@netwok.org: -- title: packaging’spysetup script should be named differently than distutils2’s pysetup - packaging’s pysetup script should be named differently than distutils2’s pysetup ___ Python tracker