Problem pyton PIL
Hi! I finally managed to install ImageMagick and Python PIL. At least I thought so. But when I do: $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type help, copyright, credits or license for more information. from PIL import Image I get this error message: Traceback (most recent call last): File stdin, line 1, in module File /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/Image.py, line 53, in module from PIL import _imaging as core ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so, 2): Symbol not found: _jpeg_resync_to_restart Referenced from: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so Expected in: dynamic lookup I have virtually no experience with MacPorts nor with Python. I just wanted to use a pythonscript which requires the image library. But that gives: ImportError: No module named Image Is here anyone who can give advice? I'm using OS X 10.5.8, MacPorts 2.2.1 and already did a ports selfupdate ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Tue, Apr 15, 2014 at 9:00 AM, Spinxer spin...@wolke7.net wrote: $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin You're getting /usr/bin/python (Apple's build). No idea what's up with its PIL. You probably want `sudo port select --set python python27; hash -r` to (a) set MacPorts python as default and (b) tell your shell to check $PATH again instead of using the Apple one it found before. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Am 15.04.14 15:20, schrieb Brandon Allbery: On Tue, Apr 15, 2014 at 9:00 AM, Spinxer spin...@wolke7.net mailto:spin...@wolke7.net wrote: $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin You're getting /usr/bin/python (Apple's build). No idea what's up with its PIL. No. Sorry, forgot to mention but sudo port select --set python python27; hash -r I already did. But to be safe I redid: $ sudo port select --set python python27; hash -r Password: Selecting 'python27' for 'python' succeeded. 'python27' is now active. $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type help, copyright, credits or license for more information. from PIL import Image Traceback (most recent call last): File stdin, line 1, in module File /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/Image.py, line 53, in module from PIL import _imaging as core ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so, 2): Symbol not found: _jpeg_resync_to_restart Referenced from: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so Expected in: dynamic lookup ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
$ sudo port select --set python python27; hash -r Password: Selecting 'python27' for 'python' succeeded. 'python27' is now active. $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type help, copyright, credits or license for more information. from PIL import Image Traceback (most recent call last): File stdin, line 1, in module File /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/Image.py, line 53, in module from PIL import _imaging as core ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so, 2): Symbol not found: _jpeg_resync_to_restart Referenced from: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so Expected in: dynamic lookup Looks like you are still not getting MacPorts python there. You should see something like macmini ~ which python /opt/local/bin/python macmini ~ /usr/bin/python Python 2.7.5 (default, Aug 25 2013, 00:04:04) [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on darwin Type help, copyright, credits or license for more information. what does 'which python' give you ? Have you added macPorts bin prefix (/opt/local/bin by default) to your PATH macmini ~ echo $PATH /opt/local/bin:/opt/local/sbin:/Users/chris/bin/:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin Chris ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Since you’re able to use port but the wrong python is picked up, it sounds like MacPorts was put as a suffix rather than prefix. As Chris said, consider sharing: echo $PATH You might also check: which -a python On Apr 15, 2014, at 9:31, Chris Jones jon...@hep.phy.cam.ac.uk wrote: macmini ~ echo $PATH /opt/local/bin:/opt/local/sbin:/Users/chris/bin/:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/opt/X11/bin ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Am 15.04.14 15:31, schrieb Chris Jones: Looks like you are still not getting MacPorts python there. You should see something like macmini ~ which python /opt/local/bin/python Okay… That gives me: $ which python /Library/Frameworks/Python.framework/Versions/2.7/bin/python Have you added macPorts bin prefix (/opt/local/bin by default) to your PATH No. I was under the impression that the sudo port select --set python python27 does everything for me so that the default python is now macports' python. So if I understood correct this is NOT the case. So what ist the command good for? Anyhow: $ /opt/local/bin/python Python 2.7.6 (default, Apr 14 2014, 14:18:39) [GCC 4.2.1 (Apple Inc. build 5566)] on darwin Type help, copyright, credits or license for more information. from PIL import Image So it seems you are right and using the full path for python (or putting the path into PATH) should help. Thanks for that. If anyone can point me to the information what's sudo port select --set python python27 good for, I think it would be perfect. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Problem pyton PIL
On Tue, Apr 15, 2014 at 9:00 AM, Spinxer spinxer at wolke7.net wrote: $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin You're getting /usr/bin/python (Apple's build). No idea what's up with its PIL. You probably want `sudo port select --set python python27; hash -r` to (a) set MacPorts python as default and (b) tell your shell to check $PATH again instead of using the Apple one it found before. That's not /usr/bin/python, as that would be 2.5 on Leopard. But it's clearly also not (an up-to-date) MacPorts python2.7 since that would be 2.7.6. - Josh ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Hi, On 15/04/14 14:41, Spinxer wrote: Am 15.04.14 15:31, schrieb Chris Jones: Looks like you are still not getting MacPorts python there. You should see something like macmini ~ which python /opt/local/bin/python Okay… That gives me: $ which python /Library/Frameworks/Python.framework/Versions/2.7/bin/python So, do you have that path in your $PATH (it will really help if you sent what echo $PATH gives ) Have you added macPorts bin prefix (/opt/local/bin by default) to your PATH No. I was under the impression that the sudo port select --set python python27 does everything for me so that the default python is now macports' python. No. When ports like pythonXY provide multiple different versions, they get installed under your installation prefix (e.g.. /opt/local) with versioned names. Port select just makes symlinks of these to unversioned names. e.g. macmini /opt/local/bin sudo port select python python27 Selecting 'python27' for 'python' succeeded. 'python27' is now active. macmini /opt/local/bin ls -lth python lrwxr-xr-x 1 root admin24B 15 Apr 14:41 python - /opt/local/bin/python2.7 macmini /opt/local/bin sudo port select python python26 Selecting 'python26' for 'python' succeeded. 'python26' is now active. macmini /opt/local/bin ls -lth python lrwxr-xr-x 1 root admin24B 15 Apr 14:42 python - /opt/local/bin/python2.6 You still have to make sure /opt/local/bin is first in your path, to make sure you pick up preferentially the MacPorts versions over anything else. So if I understood correct this is NOT the case. So what ist the command good for? It does exactly what you want. Chris Anyhow: $ /opt/local/bin/python Python 2.7.6 (default, Apr 14 2014, 14:18:39) [GCC 4.2.1 (Apple Inc. build 5566)] on darwin Type help, copyright, credits or license for more information. from PIL import Image So it seems you are right and using the full path for python (or putting the path into PATH) should help. Thanks for that. If anyone can point me to the information what's sudo port select --set python python27 good for, I think it would be perfect. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Tue, Apr 15, 2014 at 9:34 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: You might also check: which -a python Could people please stop recommending `which`? It is likely to show what your dotfiles would do in the next shell started, NOT what the current shell thinks. (Some versions will show what the next *login* would get, not just the next shell in a session, depending on whether it starts as a login shell or not.) `type` is definitive for the current shell. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Am 15.04.14 15:45, schrieb Chris Jones:
So, do you have that path in your $PATH (it will really help if you
sent what
echo $PATH
gives )
$ echo $PATH
/Library/Frameworks/Python.framework/Versions/2.7/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/Users/shk/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/opt/local/bin:/usr/local/git/bin:/opt/local/sbin:/usr/local/sbin:/Applications/wiimms-wbfs-tool/bin:/Applications/Vagrant/bin:/usr/local/mysql/bin
So the 2.7 of my Python.framework is in the path
# Setting PATH for Python 2.7
# The orginal version is saved in .profile.pysave
PATH=/Library/Frameworks/Python.framework/Versions/2.7/bin:${PATH}
export PATH
No. When ports like pythonXY provide multiple different versions, they
get installed under your installation prefix (e.g.. /opt/local) with
versioned names. Port select just makes symlinks of these to
unversioned names. e.g.
Okay. Understood. Thanks for explaining.
I changed my .profile now, so the path now is
/opt/local/bin:/Users/shk/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin/usr/local/git/bin:/opt/local/sbin:/usr/local/sbin:/Applications/wiimms-wbfs-tool/bin:/Applications/Vagrant/bin:/usr/local/mysql/bin
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Apr 15, 2014, at 08:00, Spinxer wrote: But when I do: $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type help, copyright, credits or license for more information. from PIL import Image I get this error message: Traceback (most recent call last): File stdin, line 1, in module File /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/Image.py, line 53, in module from PIL import _imaging as core ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so, 2): Symbol not found: _jpeg_resync_to_restart Referenced from: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so Expected in: dynamic lookup Where did /Library/Frameworks/Python.framework come from? It’s not provided by Apple, nor any MacPorts port, and will likely interfere with things you want to install using MacPorts. I recommend you remove it. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Hi, /opt/local/bin:/Users/shk/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin/usr/local/git/bin:/opt/local/sbin:/usr/local/sbin:/Applications/wiimms-wbfs-tool/bin:/Applications/Vagrant/bin:/usr/local/mysql/bin If thats an exact representation of what you have, then you need a : in the middle of /usr/X11/bin/usr/local/git/bin Chris ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Could people please stop recommending `which`? It is likely to show what your dotfiles would do in the next shell started, NOT what the current shell thinks. (Some versions will show what the next *login* would get, not just the next shell in a session, depending on whether it starts as a login shell or not.) `type` is definitive for the current shell. Sorry…. Yes, I know this but, somehow old habits die hard… smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Traceback (most recent call last): File stdin, line 1, in module File /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/Image.py, line 53, in module from PIL import _imaging as core ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so, 2): Symbol not found: _jpeg_resync_to_restart Referenced from: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/PIL/_imaging.so Expected in: dynamic lookup Where did /Library/Frameworks/Python.framework come from? It’s not provided by Apple, nor any MacPorts port, and will likely interfere with things you want to install using MacPorts. I recommend you remove it. Looks like it comes direct from ‘MacPython’ e.g. https://docs.python.org/2.7/using/mac.html ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
In article eef83644-0c87-444d-855e-9be25ee72...@macports.org, Ryan Schmidt ryandes...@macports.org wrote: On Apr 15, 2014, at 08:00, Spinxer wrote: But when I do: $ python Python 2.7 (r27:82508, Jul 3 2010, 21:12:11) [GCC 4.0.1 (Apple Inc. build 5493)] on darwin Type help, copyright, credits or license for more information. from PIL import Image I get this error message: Traceback (most recent call last): File stdin, line 1, in module File /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packa ges/PIL/Image.py, line 53, in module from PIL import _imaging as core ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site- packages/PIL/_imaging.so, 2): Symbol not found: _jpeg_resync_to_restart Referenced from: /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packag es/PIL/_imaging.so Expected in: dynamic lookup Where did /Library/Frameworks/Python.framework come from? It¹s not provided by Apple, nor any MacPorts port, and will likely interfere with things you want to install using MacPorts. I recommend you remove it. /Library/Frameworks/Python.framework is the installation location for the Pythons provided by python.org binary installers. They will happily co-exist with MacPorts- and Apple-provided Pythons. That said, 2.7.0 is quite old, so consider upgrading it or deleting it if you are now just going to be using a MacPorts-based Python 2.7. -- Ned Deily, n...@acm.org ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Apr 15, 2014, at 14:00, Ned Deily wrote: Ryan Schmidt wrote: Where did /Library/Frameworks/Python.framework come from? It¹s not provided by Apple, nor any MacPorts port, and will likely interfere with things you want to install using MacPorts. I recommend you remove it. /Library/Frameworks/Python.framework is the installation location for the Pythons provided by python.org binary installers. They will happily co-exist with MacPorts- and Apple-provided Pythons. Anything installed in /Library/Frameworks can potentially cause problems for MacPorts-installed software, as it might inadvertently find dependencies in /Library/Frameworks instead of the MacPorts-provided version thereof. This is similar to the /usr/local problem. That said, 2.7.0 is quite old, so consider upgrading it or deleting it if you are now just going to be using a MacPorts-based Python 2.7. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Am 15.04.14 19:58, schrieb Christopher Jones: If thats an exact representation of what you have, then you need a : in the middle of /usr/X11/bin/usr/local/git/bin Chris Well spotted! Thanks a lot! ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Am 15.04.14 19:10, schrieb Ryan Schmidt: Where did /Library/Frameworks/Python.framework come from? It’s not provided by Apple, Are you sure? Cite: The Apple-provided build of Python is installed in /System/Library/Frameworks/Python.framework and /usr/bin/python, respectively. You should never modify or delete these, as they are Apple-controlled and are used by Apple- or third-party software. Found here: https://docs.python.org/2/using/mac.html ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
/System/Library is not /Library. On Apr 15, 2014, at 16:25, Spinxer spin...@wolke7.net wrote: Where did /Library/Frameworks/Python.framework come from? It’s not provided by Apple, Are you sure? Cite: The Apple-provided build of Python is installed in /System/Library/Frameworks/Python.framework and /usr/bin/python, respectively. You should never modify or delete these, as they are Apple-controlled and are used by Apple- or third-party software. Found here: https://docs.python.org/2/using/mac.html ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Tue, Apr 15, 2014 at 4:25 PM, Spinxer spin...@wolke7.net wrote: Am 15.04.14 19:10, schrieb Ryan Schmidt: Where did /Library/Frameworks/Python.framework come from? It’s not provided by Apple, Are you sure? Cite: The Apple-provided build of Python is installed in /System/Library/Frameworks/ Read your own message? /Library is not /System/Library. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
Am 15.04.14 22:27, schrieb Jeremy Lavergne: /System/Library is not /Library. Am 15.04.14 22:28, schrieb Brandon Allbery: Read your own message? /Library is not /System/Library. *SIGH*… I think my System's broken :D I also have Python 2.7.app in /Applications In /Library/Receipts/ I find several Python*-2.7.pkg from November last year… I must have done something there. Thanks for all your support and pointing at my mistakes. I'll try now to get rid of the /Library python… ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Apr 15, 2014, at 12:36 , Ryan Schmidt ryandes...@macports.org wrote: On Apr 15, 2014, at 14:00, Ned Deily wrote: Ryan Schmidt wrote: Where did /Library/Frameworks/Python.framework come from? It?s not provided by Apple, nor any MacPorts port, and will likely interfere with things you want to install using MacPorts. I recommend you remove it /Library/Frameworks/Python.framework is the installation location for the Pythons provided by python.org binary installers. They will happily co-exist with MacPorts- and Apple-provided Pythons. Anything installed in /Library/Frameworks can potentially cause problems for MacPorts-installed software, as it might inadvertently find dependencies in /Library/Frameworks instead of the MacPorts-provided version thereof. This is similar to the /usr/local problem. I don't think that is very likely to be a problem with Pythons. And, if one pops up, it will likely be pointing out a port that is already broken. Python framework installations are somewhat odd ducks (and were implemented with some unfortunate choices). One might think that there is a risk that a port trying to link with a Python shared framework library might get the wrong library. But because there is a /System/Library/Python.framework (Apple-supplied) and the header and the default link search order include both /Library/Frameworks and /System/Library/Frameworks, ports need to be careful to use the MacPorts locations regardless of whether a /Library/Frameworks/Python.framework exists, e.g. otherwise they'll always incorrectly build/link against either the python.org or the Apple-supplied one. Secondly, using -framework Python as arguments to compile or link is almost always problematic because Python abuses the use of framework versions. Currently, all Python versions (2.x and 3.x) are installed to the same framework which, AFAICT, makes it nearly impossible to use -framework Python if you want to build or link against a specific Python version, which you almost always want to do. Instead, build scripts need to use pythonx.y-configure commands to find the proper --includes, --libs, etc, which also work in a platform-independent manner. Upstream packages that don't do so are broken and probably do not link correctly without portfile patching already. -- Ned Deily n...@acm.org -- [] -- Ned Deily, n...@acm.org ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Problem pyton PIL
On Apr 15, 2014, at 21:00, Ned Deily wrote: On Apr 15, 2014, at 12:36 , Ryan Schmidt wrote: Anything installed in /Library/Frameworks can potentially cause problems for MacPorts-installed software, as it might inadvertently find dependencies in /Library/Frameworks instead of the MacPorts-provided version thereof. This is similar to the /usr/local problem. I don't think that is very likely to be a problem with Pythons. And, if one pops up, it will likely be pointing out a port that is already broken. Python framework installations are somewhat odd ducks (and were implemented with some unfortunate choices). One might think that there is a risk that a port trying to link with a Python shared framework library might get the wrong library. But because there is a /System/Library/Python.framework (Apple-supplied) and the header and the default link search order include both /Library/Frameworks and /System/Library/Frameworks, ports need to be careful to use the MacPorts locations regardless of whether a /Library/Frameworks/Python.framework exists, e.g. otherwise they'll always incorrectly build/link against either the python.org or the Apple-supplied one. Secondly, using -framework Python as arguments to compile or link is almost always problematic because Python abuses the use of framework versions. Currently, all Python versions (2.x and 3.x) are installed to the same framework which, AFAICT, makes it nearly impossible to use -framework Python if you want to build or link against a specific Python version, which you almost always want to do. Instead, build scripts need to use pythonx.y-configure commands to find the proper --includes, --libs, etc, which also work in a platform-independent manner. Upstream packages that don't do so are broken and probably do not link correctly without portfile patching already. You may be correct about Python.framework specifically; I haven’t looked into it thoroughly. But as a general MacPorts policy, we don’t support users installing software in /usr/local or /Library/Frameworks because of problems we know doing so has caused others. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
