Tom Loredo <lor...@astro.cornell.edu> added the comment: > the python-32 executable has never been linked into /usr/local/bin.
What I meant by "the version pointed to" is: The "python" command in 2.6.4 produced by an "intel" universal build (whether in the framework or the install prefix) executed as 64-bit. I don't believe it linked to either python-32 or -64; I don't think those were even installed in 2.6.4. I think it was a bundle that just happened to execute as 64-bit (and provided no access to 32-bit python). So the "python" command-line behavior under 2.6.5rc2 is different from what it was for 2.6.4. I don't think this is a significant regression, as the previous behavior was never documented and was actually somewhat problematic. I'm just pointing it out for documentation purposes. > I always add the framework to $PATH because distutils installs scripts into > that location. Yes, I do the same. Still, I think your proposed plans for linking in the prefix in 2.7/3.2 make a lot of sense. ---------- versions: +Python 2.6 -Python 3.1 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8089> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com