python_select should create symlinks for all executables installed by python

[macports@…]

python_select does not create a symlink for easy_install like the other Python binaries. If the default interpreter is not the same minor version as the interpreter in the shebang line, easy_install will fail late with an unhelpful error message.

python_select also does not create a symlink for 2to3, but that tool appears not to be affected by the default interpreter.

[raimue (Rainer Müller)]

CC'ing maintainers of python{24,25,26,30,31}: I am going to make the necessary changes to both python_select and your ports if nobody objects.

2to3 is definitely a good idea. But I am unsure about easy_install. When using this application, won't it interfere with MacPorts installed modules and should therefore not be used? Please give advice.

[blb@…]

2to3 is fine, but note that easy_install comes from setuptools, not the base python* ports.

[speed.rob@…]

Replying to raimue@…:

2to3 is definitely a good idea. But I am unsure about easy_install. When using this application, won't it interfere with MacPorts installed modules and should therefore not be used? Please give advice.

The easy_install tool is installed with setuptools regardless, creating a symlink would only serve to override the OS X copy (which installs modules into a path that the Macports-distributed Python doesn't use). In any case, Python was designed to have modules installed in this way. It's simply not reasonable to expect every python module to have a package in Macports.

[jmroot (Joshua Root)]

r78591