[issue3646] MacOS X framework install to non-standard directory fails

Ronald Oussoren added the comment: Installing a framework anywhere but a reasonably standard location doesn't work. You should try to build with "--enable-framework=$SOMEPREFIX/Library/Frameworks". Applications then get installed in "$SOMEPREFIX/Applications" and command-line tools in "$SOME

[issue3646] MacOS X framework install to non-standard directory fails

Amos Anderson added the comment: I believe I applied the patch correctly to my Python-2.6.5.tar.bz2, on my OSX 10.6.3 machine, configured with: ./configure --enable-framework=/Users/amos/triad/trunk/src/python but "make install" now fails with this error at the end: ln: /usr/local/bin/python2

[issue3646] MacOS X framework install to non-standard directory fails

Ronald Oussoren added the comment: Als committed this for 3.2: r80648. -- stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker ___ _

[issue3646] MacOS X framework install to non-standard directory fails

Ronald Oussoren added the comment: In r80647 (trunk) you can use "configure --enable-framework=$HOME/Library/Frameworks" to get the right situation: - Framework in ~/Library/Frameworks - Apps in ~/Applications/Python 2.7 - Command-line tools in ~/bin I will port this to 3.2 later on, but won'

[issue3646] MacOS X framework install to non-standard directory fails

John-Michael Glenn added the comment: I'm using Python 2.6.4 on OSX 10.6 and I first used the mv command to rename the original python.framework. Then I was able to install 2.6 as the new python.framework. These are the commands: rename it: sudo mv /Library/Frameworks/Python.framework /Libra

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: On second thought, are you sure that's how fullinstall is meant to work? If I use frameworkinstall I get the following message at the end: * Note: not installed as 'python'. * Use 'make fullinstall' to install as 'python'. * However, 'make fullinstall' is discou

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: Ah, that makes sense - thanks for clarifying. And I was mistaken about 2.6, the no-suffix symlinks are there in $PREFIX/bin so all is good. Let me know what you think of the patch when you get a chance to look at it. -- ___

[issue3646] MacOS X framework install to non-standard directory fails

Ronald Oussoren added the comment: For 3.1 I need to check if the right files get install into the various 'bin' directories. At the languages summit at PyCon'09 the consensus seemed to be that the command-line interpreter for Python 3.x should be "python3" and that "python" would always refe

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: I was a bit surprised myself but I've just double-checked and it seems to work fine. I started with a freshly unpacked 3.0.1 tarball and used the following command: ./configure --enable-toolbox-glue --enable-universalsdk --enable-framework=/tmp/python-3.0.1-ins

[issue3646] MacOS X framework install to non-standard directory fails

Ronald Oussoren added the comment: Uploading a patch is fine, my comment was just a warning that your patch won't be applied in the repository (at least not for 2.4 and 2.5). I will look at your patch for 2.6 in the near future. Are you sure that the issue is fixed in 3.x? AFAIK that would b

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: I had a hunch that might be the case. I'm still planning to upload them here for the benefit of others who, like me, have to maintain those versions as framework installs. Is that OK? -- ___ Python tracker

[issue3646] MacOS X framework install to non-standard directory fails

Ronald Oussoren added the comment: Julian: patches for 2.4 and 2.5 will not be accepted, both releases are in "critical security fixes only" mode. -- ___ Python tracker ___

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: Attached a fix for release26-maint branch. I've tested this as follows: ./configure --enable-toolbox-glue --enable-universalsdk --enable-framework=/tmp/python-2.6-maint-install/Library/Framework --prefix=/tmp/python-2.6-maint-install && make -j3 && make framewo

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: Actually this seems to be fixed in 3.0.1 - yay! -- versions: -Python 3.0 ___ Python tracker ___ ___

[issue3646] MacOS X framework install to non-standard directory fails

Julian Scheid added the comment: The same issue is present in 2.4 and 2.5 as well as 3.0 so I'm updating this issue accordingly (haven't tried 2.7 or 3.1). I've been working around this issue with some success and will be posting patches shortly. -- nosy: +julians37 versions: +Python 2

[issue3646] MacOS X framework install to non-standard directory fails

Changes by Ronald Oussoren : -- assignee: -> ronaldoussoren nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3646] MacOS X framework install to non-standard directory fails

New submission from Konrad Hinsen <[EMAIL PROTECTED]>: The file Mac/README in Python 2.6b3 says: Installing in another place, for instance $HOME/Library/Frameworks if you have no admin privileges on your machine, has only been tested very lightly. This can be done by configuring with --enable-