You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/easy_install.txt
+5-7Lines changed: 5 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ Please see the `setuptools PyPI page <https://pypi.python.org/pypi/setuptools>`_
35
35
for download links and basic installation instructions for each of the
36
36
supported platforms.
37
37
38
-
You will need at least Python 2.6. An ``easy_install`` script will be
38
+
You will need at least Python 3.3 or 2.7. An ``easy_install`` script will be
39
39
installed in the normal location for Python scripts on your platform.
40
40
41
41
Note that the instructions on the setuptools PyPI page assume that you are
@@ -305,8 +305,7 @@ Regardless of the technique used, the script(s) will be installed to a Scripts
305
305
directory (by default in the Python installation directory). It is recommended
306
306
for EasyInstall that you ensure this directory is in the PATH environment
307
307
variable. The easiest way to ensure the Scripts directory is in the PATH is
308
-
to run ``Tools\Scripts\win_add2path.py`` from the Python directory (requires
309
-
Python 2.6 or later).
308
+
to run ``Tools\Scripts\win_add2path.py`` from the Python directory.
310
309
311
310
Note that instead of changing your ``PATH`` to include the Python scripts
312
311
directory, you can also retarget the installation location for scripts so they
@@ -987,21 +986,20 @@ The following section lists only the easiest and most relevant approaches [1]_.
987
986
988
987
`Use "virtualenv"`_
989
988
990
-
.. [1] There are older ways to achieve custom installation using various ``easy_install`` and ``setup.py install`` options, combined with ``PYTHONPATH`` and/or ``PYTHONUSERBASE`` alterations, but all of these are effectively deprecated by the User scheme brought in by `PEP-370`_ in Python 2.6.
989
+
.. [1] There are older ways to achieve custom installation using various ``easy_install`` and ``setup.py install`` options, combined with ``PYTHONPATH`` and/or ``PYTHONUSERBASE`` alterations, but all of these are effectively deprecated by the User scheme brought in by `PEP-370`_.
With Python 2.6 came the User scheme for installation, which means that all
998
-
python distributions support an alternative install location that is specific to a user [2]_ [3]_.
996
+
Python provides a User scheme for installation, which means that all
997
+
python distributions support an alternative install location that is specific to a user [3]_.
999
998
The Default location for each OS is explained in the python documentation
1000
999
for the ``site.USER_BASE`` variable. This mode of installation can be turned on by
1001
1000
specifying the ``--user`` option to ``setup.py install`` or ``easy_install``.
1002
1001
This approach serves the need to have a user-specific stash of packages.
1003
1002
1004
-
.. [2] Prior to Python2.6, Mac OS X offered a form of the User scheme. That is now subsumed into the User scheme introduced in Python 2.6.
1005
1003
.. [3] Prior to the User scheme, there was the Home scheme, which is still available, but requires more effort than the User scheme to get packages recognized.
1006
1004
1007
1005
Use the "--user" option and customize "PYTHONUSERBASE"
0 commit comments