Python on the RDP - Revision history

Ed at 19:43, 29 March 2019

2019-03-29T19:43:33Z

OliverC: /* Simultaneously Registering Python 2 and 3 */

2017-11-21T19:07:21Z

Simultaneously Registering Python 2 and 3

OliverC: /* Simultaneously Registering Python 2 and 3 */

2017-11-21T19:01:18Z

Simultaneously Registering Python 2 and 3

OliverC: /* Manually Defining Explicit Python Binary Executables */

2017-11-21T18:59:40Z

Manually Defining Explicit Python Binary Executables

OliverC at 18:58, 21 November 2017

2017-11-21T18:58:47Z

OliverC: Created page with "There are two production versions of Python: Python 2 and Python 3. * You can run scripts written for 3 with 2 if you import the special package [https://docs.python.org/2/li..."

2017-11-21T18:42:57Z

Created page with "There are two production versions of Python: Python 2 and Python 3. * You can run scripts written for 3 with 2 if you import the special package [https://docs.python.org/2/li..."

New page

There are two production versions of Python: Python 2 and Python 3.

* You can run scripts written for 3 with 2 if you import the special package [https://docs.python.org/2/library/__future__.html <code>__future__</code>]
* You can run scripts written for 2 with 3 if you run the script [https://docs.python.org/3.1/library/2to3.html <code>2to3</code>]
* '''All new code should be written in Python 3''' for library support and maintainability reasons. If for no other reason know that it uses UTF-8 as the default encoding and so it makes your life easier in every possible way.

== Installation ==

Many Python modules are actually 90% low-level C code with the remaining 10% a python wrapper.
That means to install these modules (e.g. numpy, scipy, hdf) you need to have all of the development libraries and compiler tools to compile the C stuff.
Enter [https://anaconda.org/ Anaconda], a widely used repackaging of Python for Windows that comes with most of the libraries you'll ever need.
In addition, they've made it easy to have two installs of Python running at once.

* Python2
** Python 2.7.14 via Anaconda2 5.0.1 for 64-bit
** Located at <code>C:\ProgramData\Anaconda2</code>*

* Python3
** Python 3.6.3 via Anaconda3 5.0.1 for 64-bit
** Located at <code>C:\ProgramData\Anaconda3</code>*

<nowiki>*</nowiki> Note that Anaconda is not installed in <code>C:\Program Files\AnacondaN</code> intentionally. Spaces in the path lead to a bunch of unpredictable errors.

← Older revision		Revision as of 19:43, 29 March 2019
Line 1:		Line 1:
		+	'''THIS PAGE APPLIES TO THE OLD RDP SERVER, NOT THE NEW AND CURRENT ONE'''
		+
	There are two production versions of Python: Python 2 and Python 3.		There are two production versions of Python: Python 2 and Python 3.

@@ Line 43: / Line 43: @@
 # Add semicolon-separated directories to Path in the lower box labeled System Variables
-[[File:Path-example.PNG]]
+See [http://mcnair.bakerinstitute.org/wiki/File:Path-example.PNG File:Path-example.PNG] for an example.
 == Explicitly Running a Specific Python Version ==

@@ Line 41: / Line 41: @@
 # Select the Advanced Tab
 # Select "Environment Variables..." at the bottom right
 # Add semicolon-separated directories to Path in the lower box labeled System Variables
 == Explicitly Running a Specific Python Version ==

@@ Line 24: / Line 24: @@
 === Manually Defining Explicit Python Binary Executables ===
-A common practice is to have a bunch of specific Python commands to force explicit behavior. For example on Ubuntu, you can choose from running python, python2, python 2.6, python2.7, python3, python3.5, etc in the shell. To emulate this behavior, copy and paste the <code>python.exe</code> and rename it to <code>pythonN.exe</code> where N is whatever specific version you copied.
+A common practice is to have a bunch of specific Python commands to force explicit behavior. For example on Ubuntu, you can choose from running python, python2, python 2.6, python2.7, python3, python3.5, etc in the shell. To emulate this behavior, copy and paste the <code>python.exe</code> and rename it to <code>pythonN.exe</code> where N is whatever specific version you copied. The same applies to scripts you want to use like <code>pip</code>: copy-and-paste the file to a more explicit name.
 Path is evaluated with the first entries taking precedence. Thus, whichever version of Python you want to be the default should be listed at the leftmost position on the string. You can also just delete the unregistered python.exe to achieve the same result.

← Older revision		Revision as of 18:58, 21 November 2017
Line 21:		Line 21:

	<nowiki>*</nowiki> Note that Anaconda is not installed in <code>C:\Program Files\AnacondaN</code> intentionally. Spaces in the path lead to a bunch of unpredictable errors.		<nowiki>*</nowiki> Note that Anaconda is not installed in <code>C:\Program Files\AnacondaN</code> intentionally. Spaces in the path lead to a bunch of unpredictable errors.
		+
		+	=== Manually Defining Explicit Python Binary Executables ===
		+
		+	A common practice is to have a bunch of specific Python commands to force explicit behavior. For example on Ubuntu, you can choose from running python, python2, python 2.6, python2.7, python3, python3.5, etc in the shell. To emulate this behavior, copy and paste the <code>python.exe</code> and rename it to <code>pythonN.exe</code> where N is whatever specific version you copied.
		+
		+	Path is evaluated with the first entries taking precedence. Thus, whichever version of Python you want to be the default should be listed at the leftmost position on the string. You can also just delete the unregistered python.exe to achieve the same result.
		+
		+	=== ArcMap Aside ===
		+
		+	Note that by default, ESRI ArcMap maintains a separate Python 2 installation at <code>C:\Python27</code>. Just ignore this...it is not to be used for development or as the environment for running programs other than ArcMap.
		+
		+	== Simultaneously Registering Python 2 and 3 ==
		+
		+	Anaconda automatically "registers" the separate installations for use with some development environments. It does not (by default) add executables to the Path system environment. We will add the base <code>AnacondaN/</code> files and <code>AnacondaN/Scripts/</code> to the path as so:
		+
		+	# Right-click on the Windows icon in the bottom left
		+	# Select System
		+	# Select Advanced System Settings (must be administrator)
		+	# Select the Advanced Tab
		+	# Select "Environment Variables..." at the bottom right
		+	# Add semicolon-separated directories to Path in the lower box labeled System Variables
		+
		+	== Explicitly Running a Specific Python Version ==
		+
		+	All of these are valid ways to run Python on the RDP:
		+
		+	* <code>python</code>
		+	* <code>python2</code>
		+	* <code>python3</code>
		+
		+	By default, running <code>python</code> will run Python 2. '''This behavior should not be relied on.''' On most other systems, Python 3 is the default instead.
		+
		+	It is the same case with <code>pip</code> which can be run via <code>pip</code>, <code>pip2</code>, <code>pip3</code>