[issue10215] Mac Python 3.1 installer does less than earlier installers

Bruce Sherwood 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

[issue10215] Mac Python 3.1 installer does less than earlier installers

Changes by Ned Deily : -- Removed message: http://bugs.python.org/msg120303 ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue10215] Mac Python 3.1 installer does less than earlier installers

Ned Deily 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 fr

[issue10215] Mac Python 3.1 installer does less than earlier installers

Ned Deily 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 fr

[issue10215] Mac Python 3.1 installer does less than earlier installers

Bruce Sherwood 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. Inciden

[issue10215] Mac Python 3.1 installer does less than earlier installers

Éric Araujo 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 framew

[issue10215] Mac Python 3.1 installer does less than earlier installers

Bruce Sherwood 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 wrote: > > Éric Araujo added the comment: > > Without typos: Does 3.1 install into a Python

[issue10215] Mac Python 3.1 installer does less than earlier installers

Éric Araujo added the comment: Without typos: Does 3.1 install into a Python3.framework directory? -- ___ Python tracker ___ ___ Pyth

[issue10215] Mac Python 3.1 installer does less than earlier installers

Éric Araujo 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

[issue10215] Mac Python 3.1 installer does less than earlier installers

Changes by R. David Murray : -- resolution: -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue10215] Mac Python 3.1 installer does less than earlier installers

R. David Murray 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 t

[issue10215] Mac Python 3.1 installer does less than earlier installers

Changes by Antoine Pitrou : -- assignee: -> ronaldoussoren nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing

[issue10215] Mac Python 3.1 installer does less than earlier installers

New submission from Bruce Sherwood : 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 wond