[issue10215] Mac Python 3.1 installer does less than earlier installers
Éric Araujo mer...@netwok.org added the comment: Does 3.2 install into a Python3.framework? In other words, is the conception that 2.x and 3.x are two different languages ported over to Mac? -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Éric Araujo mer...@netwok.org added the comment: Without typos: Does 3.1 install into a Python3.framework directory? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Bruce Sherwood bruce.sherw...@gmail.com added the comment: Yes. After installation, you'll see that Python 3.1 is in /Library/Frameworks/Python.framework/Versions/3.1 Bruce Sherwood On Tue, Nov 2, 2010 at 1:45 PM, Éric Araujo rep...@bugs.python.org wrote: Éric Araujo mer...@netwok.org added the comment: Without typos: Does 3.1 install into a Python3.framework directory? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Éric Araujo mer...@netwok.org added the comment: So your answer is actually *no*, it does not install into Python3.framework :) If there had been separate Python.framework and Python3.framework, the answer to this bug would be obvious. But since 2.x and 3.x Pythons are installed as versions of the same framework, it sort of makes sense that Versions/Current can point to a 3.x version. Do I make sense? -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Bruce Sherwood bruce.sherw...@gmail.com added the comment: Now I understand what you're getting at; I didn't realize that you were aiming at the possible distinction between 3 and 3.1. Yes, this is what bothered me and prompted my original posting. Python 3.1 goes into the same framework as the 2.x versions. Incidentally, I did find that in /usr/local/bin (where I had not thought to look) there are the following: python3.1, a link to the framework python3.1 pythonw3.1, a link to the framework pythonw3.1 python3, a link to a framework python3, which is an extra copy (not a link) to the framework python3.1 pythonw3, a link to a framework pythonw3, which is a link to the framework python3.1 This looks to me pretty contorted, although I suppose the goal was to let people either run python (their most recent Python 2.x) or run python3 (their most recent Python 3.x). A somewhat related example of confusion is that on Ubuntu 10.10 there is a shadowy existence for some python3 that has its own lib folder, in parallel to python3.1; the python3 doesn't seem to be simply an alias for python3.1. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Ned Deily n...@acm.org added the comment: It was a deliberate decision on Ronald's part to not modify the Versions/Current link in the Python framework when installing a Python 3.x version. As far as I know, the Current link is not used anywhere other than perhaps by Xcode when trying to link a Python frameworks into another language project. Current has no affect on any of the /usr/local symlinks optionally created by the python OS X installer. Use of the those symlinks is somewhat problematic anyway once you install any third-party packages the include scripts. By default, Distutils installs scripts into the framework bin directory of the appropriate version. That's why the recommended approach to managing paths is to simply put the framework bin directory towards the head of your shell PATH. For each version, the OS X installer provides Update Shell Profile.command to alter the most common shell profiles accordingly; it can be found in the /Applications/Python x.m folder. As documented in the installer README, for 3.x installs, the installer does not automatically run Update Shell Profile as it does for 2.x installs; you need to run it explicitly or otherwise cause PATH to be changed. -- nosy: +ned.deily ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Ned Deily n...@acm.org added the comment:
It was a deliberate decision on Ronald's part to not modify the
Versions/Current link in the Python framework when installing a Python 3.x
version. As far as I know, the Current link is not used anywhere other than
perhaps by Xcode when trying to link a Python frameworks into another language
project. Current has no affect on any of the /usr/local symlinks optionally
created by the python OS X installer.
Use of the those symlinks is somewhat problematic anyway once you install any
third-party packages that include scripts. By default, Distutils installs
scripts into the framework bin directory of the appropriate version. That's
why the recommended approach to managing paths is to simply put the framework
bin directory towards the head of your shell PATH, so something like:
export PATH=/Library/Frameworks/Python.framework/Versions/3.1/bin:${PATH}
For each version, the OS X installer provides Update Shell Profile.command to
alter the most common shell profiles accordingly; it can be found in the
/Applications/Python x.m folder. As documented in the installer README, for
3.x installs, the installer does not automatically run Update Shell Profile
as it does for 2.x installs; you need to run it explicitly or otherwise cause
PATH to be changed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10215
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Changes by Ned Deily n...@acm.org: -- Removed message: http://bugs.python.org/msg120303 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Bruce Sherwood bruce.sherw...@gmail.com added the comment: Thanks for the detailed explanation. What had not occurred to me was to read the README file that came with the installer. I made the mistake (that may be made by others) of assuming continuity with installer policy, especially since the installation location was the same as before. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
New submission from Bruce Sherwood bruce.sherw...@gmail.com: For Python 2.x on Macs, the installer added PATH code to .profile and switched /Library/Framework/Python.framework/Versions/Current to point to the newly installed version of Python. Neither of these actions is carried out by the 3.1.2 installer, and I wonder whether this is intentional or an oversight. Also, it's not clear to me what command one could issue in a terminal to execute the new Python (you can of course start the new Python from the Applications folder). -- components: Installation messages: 119731 nosy: Bruce.Sherwood priority: normal severity: normal status: open title: Mac Python 3.1 installer does less than earlier installers type: feature request versions: Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Changes by Antoine Pitrou pit...@free.fr: -- assignee: - ronaldoussoren nosy: +ronaldoussoren ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
R. David Murray rdmur...@bitdance.com added the comment: Yes this is deliberate. On linux, 'python' is Python2, and 'python3' is Python3. I'm not a mac user, so I don't know exactly how the naming conventions work there, but I certainly wouldn't expect the 'current version' of 'python' to change to python3. I think perhaps the command name you use from the terminal is the same as it is on linux: python3, but I'm not positive. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10215] Mac Python 3.1 installer does less than earlier installers
Changes by R. David Murray rdmur...@bitdance.com: -- resolution: - invalid stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10215 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
