From 5f348c9be2fa820012623bc09154d724465786f0 Mon Sep 17 00:00:00 2001 From: rroskam Date: Sun, 11 Feb 2018 10:49:26 -0600 Subject: [PATCH] Updating to use chocolatey --- docs/starting/install3/win.rst | 58 ++++------------------------------ 1 file changed, 7 insertions(+), 51 deletions(-) diff --git a/docs/starting/install3/win.rst b/docs/starting/install3/win.rst index 139b30259..ddddad5fa 100644 --- a/docs/starting/install3/win.rst +++ b/docs/starting/install3/win.rst @@ -5,61 +5,17 @@ Installing Python 3 on Windows .. image:: https://farm5.staticflickr.com/4276/34435689480_2e6f358510_k_d.jpg -First, download the `latest version `_ -of Python 3.6 from the official website. If you want to be sure you are installing a fully -up-to-date version, click the Downloads > Windows link from the home page of the -`Python.org web site `_. - -By design, Python installs to a directory with the version number embedded, -e.g. Python version 3.6 will install at :file:`C:\\Python36\\`, so that you can -have multiple versions of Python on the -same system without conflicts. Of course, only one interpreter can be the -default application for Python file types. It also does not automatically -modify the :envvar:`PATH` environment variable, so that you always have control over -which copy of Python is run. - -Typing the full path name for a Python interpreter each time quickly gets -tedious, so add the directories for your default Python version to the :envvar:`PATH`. -Assuming that your Python installation is in :file:`C:\\Python36\\`, add this to your -:envvar:`PATH`: +First, follow the installation instructions for `Chocolatey `_. +It's a community system packager manager for Windows 7+. (It's very much like Homebrew on OSX.) -.. code-block:: console - - C:\Python36\;C:\Python36\Scripts\ - -You can do this easily by running the following in ``powershell``: +Once done, installing Python 3 is very simple, because Chocolatey pushes Python 3 as the default. .. code-block:: console - [Environment]::SetEnvironmentVariable("Path", "$env:Path;C:\Python36\;C:\Python36\Scripts\", "User") - -This is also an option during the installation process. - -The second (:file:`Scripts`) directory receives command files when certain -packages are installed, so it is a very useful addition. -You do not need to install or configure anything else to use Python. Having -said that, I would strongly recommend that you install the tools and libraries -described in the next section before you start building Python applications for -real-world use. In particular, you should always install Setuptools, as it -makes it much easier for you to use other third-party Python libraries. - -Working with Python 3 ---------------------- - -At this point, you may also have Python 2.7 installed. - -.. code-block:: console - - $ python - -This will launch the Python 2 interpreter. - -.. code-block:: console - - $ python3 - -This will launch the Python 3 interpreter. + choco install python +Once you've run this command, you should be able to launch Python directly from to the console. +(Chocolatey is fantastic and automatically adds Python to your path.) Setuptools + Pip ---------------- @@ -84,7 +40,7 @@ in separate places, by creating virtual Python environments for them. It solves "Project X depends on version 1.x but, Project Y needs 4.x" dilemma, and keeps your global site-packages directory clean and manageable. -For example, you can work on a project which requires Django 1.10 while also +For example, you can work on a project which requires Django 2.0 while also maintaining a project which requires Django 1.8. So, onward! To the :ref:`Pipenv & Virtual Environments ` docs!