Homebrew brew doctor warns of /Library/Frameworks/Python.framework, even with Python brew installed

When I started the Homebrew brew doctor (Mac OS X 10.9.2), the following warning message appears:

Warning: Python is installed in /Library/Frameworks/Python.framework

Homebrew only supports Python-based creation or brewing python. In particular, Pythons installed in / Library may interfere with other software installations.

So I ran brew install and followed the steps in the output of the installation caveat to install the version of Homebrew Python . Running which python confirms that the Homebrew version is indeed at the top of my PATH. The output is /usr/local/bin/python .

Despite all this, when I restart the brew doctor , I still get the same warning. How can I suppress this warning? Do I need to remove the /Library/Frameworks/Python.framework directory from my computer? Should I just ignore it? Is there another application on my computer that might trigger this warning?

Please note that I do not have applications running errors due to this warning from brew doctor . Also note that this warning was not always printed when I ran the brew doctor , it was something that has appeared recently. Also, I am using Python 2.7 on my computer, trying to stay away from Python 3.

+66
python homebrew macos
Mar 07 '14 at 16:33
source share
5 answers

I had the same problem. When I upgraded python3 via Homebrew, I started getting this:

 -bash: python3: command not found 

I had the same conflict with Python that was somehow installed in /Library/Framework/Python.framework . I just did a brew link overwrite and now everything is working fine. There is some information on what to do with the Python version in /Library/Framework/Python.framework here .

I think you could try uninstalling this version by reference, just make sure the version is not in use. When I got into the Python.framework directory, I saw an EPD version of Python, which I think is Enthought. You can delete it, but I, if it does not cause you any problems besides the unsightly warning message Homebrew, then I think you should just ignore it now.

Update:

I deleted the Python.framework directory, which through some of them was torn out inside this directory, I began to see several old versions of Python that I did not install using Homebrew. One was from Enthought, and the other was a Python3.3 distribution. I think some of these settings in the Framework directory are user settings. I installed R on my system, and there is also an R.framework directory, so I think most of them are custom installations. After I deleted the directory, I just had to call brew a draft to delete the old symbolic links. I checked both brew versions of python versions 2.7.6 and 3.3.4, and they seem to be in good working condition with all my packages installed. I guess I leave the decision to remove this directory or python version of your choice.

+29
Mar 08 '14 at 4:50
source share
— -

I also received this message.

Something Once Established

/Library/Frameworks/Python.framework

on my machine (the folder date was about 4 years).

I decided to remove it.

Please note that the infrastructure provided by Apple lives in

/System/Library/Frameworks/Python.framework/

+34
Mar 12 '14 at 15:09
source share

per this thread , enter the following command:

sudo rm -rf /Library/Frameworks/Python.framework

since there are several Python installations installed on your computer, and this fixes a problem that might cause additional problems in the future.

+17
Jul 08 '14 at 1:30
source share

You can use this solution as I said below

 sudo rm -rf /Library/Frameworks/Python.framework brew doctor brew prune brew update 

This combo fixed it for me, I even thought that this error usually does not cause any serious problems, it just annoyed me to pop up under the brew doctor

+13
Dec 07 '15 at
source share

Manually deleting directories can be a nightmare, but luckily brew can take care of that. When you finish uninstalling, put this:

 brew doctor 

The above command lists broken system links. To get rid of these broken symbolic links, put this:

 brew prune 

See your brew doctor again to make sure the links are not broken. Then your system will be ready for brew.

+2
Aug 14 '15 at 16:46
source share



All Articles