Mac os python library path

patriciogonzalezvivo / PythonSetup.md

After installing pyqt, Homebrew will prompt you to add the following to your .bash_profile:

export PYTHONPATH=/usr/local/lib/python:$PYTHONPATH 

Keep installing dependences for PyQT

brew install zmq pip install pyzmq pip install pygments 

1. Download and Install Sublime
2. Edit Python paths.
   • Sublime >> Preferences. >> Browse Packages.
   • Click on Python/Python.sublime-build
3. Install PackageControl. The simplest method of installation is through the Sublime Text console. The console is accessed via the ctrl+ shortcut or the View > Show Console menu`. Once open, paste the appropriate Python code for your version of Sublime Text into the console.

import urllib2,os,hashlib; h = '7183a2d3e96f11eeadd761d777e62404' + 'e330c659d4bb41d3bdf022e94cab3cd0'; pf = 'Package Control.sublime-package'; ipp = sublime.installed_packages_path(); os.makedirs( ipp ) if not os.path.exists(ipp) else None; urllib2.install_opener( urllib2.build_opener( urllib2.ProxyHandler()) ); by = urllib2.urlopen( 'http://sublime.wbond.net/' + pf.replace(' ', '%20')).read(); dh = hashlib.sha256(by).hexdigest(); open( os.path.join( ipp, pf), 'wb' ).write(by) if dh == h else None; print('Error validating download (got %s instead of %s), please try manual install' % (dh, h) if dh != h else 'Please restart Sublime Text to finish installation') 

< "env":< "PATH":"/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/bin:/usr/local/share/python", "PYTHONPATH":"/usr/local/lib/python:/usr/local/Cellar/python/2.7.2/lib/python2.7/site-packages" >, "cmd": ["/usr/local/bin/python", "-u", "$file"], "file_regex": "^[ ]*File \"(. *?)\", line (4*)", "selector": "source.python" > 

Python Autocompletion with SublimeCodeIntel

Once you install Package Control, restart ST2 and bring up the Command Palette (Command+Shift+P on OS X, Control+Shift+P on Linux/Windows). Select «Package Control: Install Package», wait while Package Control fetches the latest package list, then select SublimeCodeIntel when the list appears. The advantage of using this method is that Package Control will automatically keep SublimeCodeIntel up to date with the latest version.

because of https://github.com/Homebrew/homebrew-science/issues/1291#issuecomment-60704018 you should replace brew install gfortran with brew install gcc .

~ brew install gfortran Error: No available formula for gfortran GNU Fortran is now provided as part of GCC, and can be installed with: brew install gcc 

I’ve read that gcc shouldn’t be installed if you also have Xcode installed.

Xcode does not provide any Fortran, so you really will need gfortran (and thus gcc) if you need it.

As of now, this does not work anymore. On macOS with Homebrew you have to set the path as follows:

export PATH="/usr/local/opt/python/libexec/bin:$PATH" 

Otherwise the system python will come first. Check brew info python for the caveats.

After adding a path to ~/.bash_profile, you have to run source ~/.bash_profile in the terminal. Otherwise, the change doesn’t register.

Hi, I have already Python 2.7 & 3.5 on my Mac. I have been writing python programs using the IDLE.
I now have need to install ‘Homebrew’ — I didn’t previously know about ‘Homebrew’ as I am new to programming.
When I try to install ‘Homebrew’ on the command line it fails.
When I run ‘brew doctor’ I get the following warnings:

Warning: «config» scripts exist outside your system or Homebrew directories.
./configure scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following «config» scripts:
/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5m-config
/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5-config
/Library/Frameworks/Python.framework/Versions/3.5/bin/python3-config
/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2-config
/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7-config
/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python-config

If I uninstall both versions of Python and then reinstall using ‘Homebrew’ I will lose months of work, is there another way around this?

Hello @patriciogonzalezvivo,

because of Homebrew/homebrew-science#1291 (comment) you should replace brew install gfortran with brew install gcc.

~ brew install gfortran
Error: No available formula for gfortran
GNU Fortran is now provided as part of GCC, and can be installed with:
brew install gcc
Happy coding,
Darius

Maybe you try this:
brew cask install gfortran

As of now, this does not work anymore. On macOS with Homebrew you have to set the path as follows:

export PATH="/usr/local/opt/python/libexec/bin:$PATH" 

Otherwise the system python will come first. Check brew info python for the caveats.

I also have this problem. Not sure how to get around this without having to uninstall everything and reinstall all the data sci packages. I have a feeling miniconda/anaconda messed this up. Anyway I can get miniconda and homebrew to play nice together?

What’s written below is a helpful way to install Python (+ others) on a Mac if you are doing analytics/data science.

FWIW, what is written by the OP is the «right way» for non-data scientists. If you are using Python for analytics, I recommend using Anaconda (specifically Miniconda) for as much as you can, instead of Pip.

There is nothing wrong with Pip, and in fact it contains far more Python packages than Conda. However, Conda (a) primarily focuses on numerical packages, (2) it can install things outside of Python (which is a real blessing when the Python package you are installing is «just a wrapper» around lower-level C or even FORTRAN packages, and (3) it does a fairly decent job of trying to find the minimally harmful clashes between versions of packages you have installed. Most data scientists, myself included, get kinda sloppy about this.

The «right way» to avoid clashes is to make a separate virtual environment for each different thing that you’re working on, but as data scientists, we’re often working with packages only as long as it takes us to realize we didn’t like the results. but we might like that package in the future. Hence, clutter.

Inevitably, conda will not have things that you want to install. In that case, fall back on pip , but be sure to go into a conda environment before running pip , so that you install into the same place you have put all of your Python packages installed from Conda.

Unfortunately for us analysts using Macs, we have to rely upon brew , pip , and conda for installs. (And sometimes just raw downloads: I have had trouble trying to use R with conda or virtualenv .) It’s a hassle, and it doesn’t always work out, but my priority order is conda , then pip , then brew , then raw download. brew should not be needed for any Python packages, nor should a raw download.

Источник

5. Using Python on a Mac¶

Python on a Mac running macOS is in principle very similar to Python on any other Unix platform, but there are a number of additional features such as the IDE and the Package Manager that are worth pointing out.

5.1. Getting and Installing MacPython¶

macOS used to come with Python 2.7 pre-installed between versions 10.8 and 12.3. You are invited to install the most recent version of Python 3 from the Python website (https://www.python.org). A current “universal binary” build of Python, which runs natively on the Mac’s new Intel and legacy PPC CPU’s, is available there.

What you get after installing is a number of things:

• A Python 3.12 folder in your Applications folder. In here you find IDLE, the development environment that is a standard part of official Python distributions; and PythonLauncher, which handles double-clicking Python scripts from the Finder.
• A framework /Library/Frameworks/Python.framework , which includes the Python executable and libraries. The installer adds this location to your shell path. To uninstall MacPython, you can simply remove these three things. A symlink to the Python executable is placed in /usr/local/bin/.

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. Remember that if you choose to install a newer Python version from python.org, you will have two different but functional Python installations on your computer, so it will be important that your paths and usages are consistent with what you want to do.

IDLE includes a help menu that allows you to access Python documentation. If you are completely new to Python you should start reading the tutorial introduction in that document.

If you are familiar with Python on other Unix platforms you should read the section on running Python scripts from the Unix shell.

5.1.1. How to run a Python script¶

Your best way to get started with Python on macOS is through the IDLE integrated development environment, see section The IDE and use the Help menu when the IDE is running.

If you want to run Python scripts from the Terminal window command line or from the Finder you first need an editor to create your script. macOS comes with a number of standard Unix command line editors, vim and emacs among them. If you want a more Mac-like editor, BBEdit or TextWrangler from Bare Bones Software (see http://www.barebones.com/products/bbedit/index.html) are good choices, as is TextMate (see https://macromates.com/). Other editors include Gvim (https://macvim.org/macvim/) and Aquamacs (http://aquamacs.org/).

To run your script from the Terminal window you must make sure that /usr/local/bin is in your shell search path.

To run your script from the Finder you have two options:

• Drag it to PythonLauncher
• Select PythonLauncher as the default application to open your script (or any .py script) through the finder Info window and double-click it. PythonLauncher has various preferences to control how your script is launched. Option-dragging allows you to change these for one invocation, or use its Preferences menu to change things globally.

5.1.2. Running scripts with a GUI¶

With older versions of Python, there is one macOS quirk that you need to be aware of: programs that talk to the Aqua window manager (in other words, anything that has a GUI) need to be run in a special way. Use pythonw instead of python to start such scripts.

With Python 3.9, you can use either python or pythonw.

5.1.3. Configuration¶

Python on macOS honors all standard Unix environment variables such as PYTHONPATH , but setting these variables for programs started from the Finder is non-standard as the Finder does not read your .profile or .cshrc at startup. You need to create a file ~/.MacOSX/environment.plist . See Apple’s Technical Document QA1067 for details.

For more information on installation Python packages in MacPython, see section Installing Additional Python Packages .

5.2. The IDE¶

MacPython ships with the standard IDLE development environment. A good introduction to using IDLE can be found at http://www.hashcollision.org/hkn/python/idle_intro/index.html.

5.3. Installing Additional Python Packages¶

There are several methods to install additional Python packages:

• Packages can be installed via the standard Python distutils mode ( python setup.py install ).
• Many packages can also be installed via the setuptools extension or pip wrapper, see https://pip.pypa.io/.

5.4. GUI Programming on the Mac¶

There are several options for building GUI applications on the Mac with Python.

PyObjC is a Python binding to Apple’s Objective-C/Cocoa framework, which is the foundation of most modern Mac development. Information on PyObjC is available from https://pypi.org/project/pyobjc/.

The standard Python GUI toolkit is tkinter , based on the cross-platform Tk toolkit (https://www.tcl.tk). An Aqua-native version of Tk is bundled with OS X by Apple, and the latest version can be downloaded and installed from https://www.activestate.com; it can also be built from source.

wxPython is another popular cross-platform GUI toolkit that runs natively on macOS. Packages and documentation are available from https://www.wxpython.org.

PyQt is another popular cross-platform GUI toolkit that runs natively on macOS. More information can be found at https://riverbankcomputing.com/software/pyqt/intro.

5.5. Distributing Python Applications on the Mac¶

The standard tool for deploying standalone Python applications on the Mac is py2app. More information on installing and using py2app can be found at https://pypi.org/project/py2app/.

5.6. Other Resources¶

The MacPython mailing list is an excellent support resource for Python users and developers on the Mac:

Another useful resource is the MacPython wiki:

Источник