pyenv安装脚本pyenv.zip

# Simple Python Version Management: pyenv [](https://gitter.im/yyuu/pyenv?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) pyenv lets you easily switch between multiple versions of Python. It's simple, unobtrusive, and follows the UNIX tradition of single-purpose tools that do one thing well. This project was forked from [rbenv](https://github.com/rbenv/rbenv) and [ruby-build](https://github.com/rbenv/ruby-build), and modified for Python.  ### what pyenv _does..._ * Lets you **change the global Python version** on a per-user basis. * Provides support for **per-project Python versions**. * Allows you to **override the Python version** with an environment variable. * Searches for commands from **multiple versions of Python at a time**. This may be helpful to test across Python versions with [tox](https://pypi.python.org/pypi/tox). ### In contrast with pythonbrew and pythonz, pyenv _does not..._ * **Depend on Python itself.** pyenv was made from pure shell scripts. There is no bootstrap problem of Python. * **Need to be loaded into your shell.** Instead, pyenv's shim approach works by adding a directory to your `$PATH`. * **Manage virtualenv.** Of course, you can create [virtualenv](https://pypi.python.org/pypi/virtualenv) yourself, or [pyenv-virtualenv](https://github.com/pyenv/pyenv-virtualenv) to automate the process. ---- ## Table of Contents * **[How It Works](#how-it-works)** * [Understanding PATH](#understanding-path) * [Understanding Shims](#understanding-shims) * [Choosing the Python Version](#choosing-the-python-version) * [Locating the Python Installation](#locating-the-python-installation) * **[Installation](#installation)** * [Prerequisites](#prerequisites) * [Homebrew in macOS](#homebrew-in-macos) * [Windows](#windows) * [Automatic installer](#automatic-installer) * [Basic GitHub Checkout](#basic-github-checkout) * [Upgrading](#upgrading) * [Homebrew on macOS](#homebrew-on-macos) * [Advanced Configuration](#advanced-configuration) * [Uninstalling Python Versions](#uninstalling-python-versions) * **[Command Reference](#command-reference)** * **[Development](#development)** * [Version History](#version-history) * [License](#license) ---- ## How It Works At a high level, pyenv intercepts Python commands using shim executables injected into your `PATH`, determines which Python version has been specified by your application, and passes your commands along to the correct Python installation. ### Understanding PATH When you run a command like `python` or `pip`, your operating system searches through a list of directories to find an executable file with that name. This list of directories lives in an environment variable called `PATH`, with each directory in the list separated by a colon: /usr/local/bin:/usr/bin:/bin Directories in `PATH` are searched from left to right, so a matching executable in a directory at the beginning of the list takes precedence over another one at the end. In this example, the `/usr/local/bin` directory will be searched first, then `/usr/bin`, then `/bin`. ### Understanding Shims pyenv works by inserting a directory of _shims_ at the front of your `PATH`: $(pyenv root)/shims:/usr/local/bin:/usr/bin:/bin Through a process called _rehashing_, pyenv maintains shims in that directory to match every Python command across every installed version of Python—`python`, `pip`, and so on. Shims are lightweight executables that simply pass your command along to pyenv. So with pyenv installed, when you run, say, `pip`, your operating system will do the following: * Search your `PATH` for an executable file named `pip` * Find the pyenv shim named `pip` at the beginning of your `PATH` * Run the shim named `pip`, which in turn passes the command along to pyenv ### Choosing the Python Version When you execute a shim, pyenv determines which Python version to use by reading it from the following sources, in this order: 1. The `PYENV_VERSION` environment variable (if specified). You can use the [`pyenv shell`](https://github.com/pyenv/pyenv/blob/master/COMMANDS.md#pyenv-shell) command to set this environment variable in your current shell session. 2. The application-specific `.python-version` file in the current directory (if present). You can modify the current directory's `.python-version` file with the [`pyenv local`](https://github.com/pyenv/pyenv/blob/master/COMMANDS.md#pyenv-local) command. 3. The first `.python-version` file found (if any) by searching each parent directory, until reaching the root of your filesystem. 4. The global `$(pyenv root)/version` file. You can modify this file using the [`pyenv global`](https://github.com/pyenv/pyenv/blob/master/COMMANDS.md#pyenv-global) command. If the global version file is not present, pyenv assumes you want to use the "system" Python. (In other words, whatever version would run if pyenv weren't in your `PATH`.) **NOTE:** You can activate multiple versions at the same time, including multiple versions of Python2 or Python3 simultaneously. This allows for parallel usage of Python2 and Python3, and is required with tools like `tox`. For example, to set your path to first use your `system` Python and Python3 (set to 2.7.9 and 3.4.2 in this example), but also have Python 3.3.6, 3.2, and 2.5 available on your `PATH`, one would first `pyenv install` the missing versions, then set `pyenv global system 3.3.6 3.2 2.5`. At this point, one should be able to find the full executable path to each of these using `pyenv which`, e.g. `pyenv which python2.5` (should display `$(pyenv root)/versions/2.5/bin/python2.5`), or `pyenv which python3.4` (should display path to system Python3). You can also specify multiple versions in a `.python-version` file, separated by newlines. Lines starting with a `#` are ignored. ### Locating the Python Installation Once pyenv has determined which version of Python your application has specified, it passes the command along to the corresponding Python installation. Each Python version is installed into its own directory under `$(pyenv root)/versions`. For example, you might have these versions installed: * `$(pyenv root)/versions/2.7.8/` * `$(pyenv root)/versions/3.4.2/` * `$(pyenv root)/versions/pypy-2.4.0/` As far as Pyenv is concerned, version names are simply directories under `$(pyenv root)/versions`. ### Managing Virtual Environments There is a pyenv plugin named [pyenv-virtualenv](https://github.com/pyenv/pyenv-virtualenv) which comes with various features to help pyenv users to manage virtual environments created by virtualenv or Anaconda. Because the `activate` script of those virtual environments are relying on mutating `$PATH` variable of user's interactive shell, it will intercept pyenv's shim style command execution hooks. We'd recommend to install pyenv-virtualenv as well if you have some plan to play with those virtual environments. ---- ## Installation ### Prerequisites For pyenv to install python correctly you should [**install the Python build dependencies**](https://github.com/pyenv/pyenv/wiki#suggested-build-environment). ### Homebrew in macOS 1. Consider installing with [Homebrew](https://brew.sh): ```sh brew update brew install pyenv ``` 2. Then follow the rest of the post-installation steps under [Basic GitHub Checkout](https://github.com/pyenv/pyenv#basic-github-checkout), starting with #​2 ("Configure your shell's environment for Pyenv"). 3. OPTIONAL. To fix `brew doctor`'s warning _""config" scripts exist outside your system or Homebrew directories"_ If you're going to build Homebrew formulae from source that link against `libpython` like Tkinter or NumPy _(This is only gene