Python on the CS Linux Clients - Revision history

Pip: /* Note: Python 2 is Deprecated */ Python 2 removal date

2024-08-14T20:12:52Z

Note: Python 2 is Deprecated: Python 2 removal date

Phil: /* Note: Python 2 is Deprecated */

2022-05-16T17:39:54Z

Note: Python 2 is Deprecated

Phil at 14:02, 7 July 2021

2021-07-07T14:02:56Z

Phil at 14:02, 7 July 2021

2021-07-07T14:02:21Z

Phil: /* Note: Python 2 is Deprecated */

2021-07-07T14:01:00Z

Note: Python 2 is Deprecated

Steve410 at 13:27, 13 April 2020

2020-04-13T13:27:10Z

Phil: /* Note: Change in Default Python Version */

2020-02-03T16:47:52Z

Note: Change in Default Python Version

Phil: /* Note: Change in Default Python Version */

2020-02-03T16:45:59Z

Note: Change in Default Python Version

Phil: /* virtualenv */

2020-01-06T16:58:13Z

virtualenv

Phil: Update for the Python 2 to 3 transition.

2020-01-06T16:39:08Z

Update for the Python 2 to 3 transition.

@@ Line 7: / Line 7: @@
 Although Python 2.7 is installed on our systems, it should only be used when needed for compatibility with older programs.  Official support for Python 2 ended in January 2020.  New programs should use Python 3, and old Python 2 programs may not work properly.  If a program does not work with Python 2, the solution is to [https://docs.python.org/3/howto/pyporting.html port it to Python 3].
-Python 3 has been the default version of Python on our systems since early 2020.  We expect to completely remove Python 2 from our Linux clients once even the legacy packaging is no longer officially supported by our Linux distributor.
+Python 3 has been the default version of Python on our systems since early 2020.  We expect to completely remove Python 2 from our Linux clients in the summer of 2025.
 == Installing Python Packages ==

@@ Line 7: / Line 7: @@
 Although Python 2.7 is installed on our systems, it should only be used when needed for compatibility with older programs.  Official support for Python 2 ended in January 2020.  New programs should use Python 3, and old Python 2 programs may not work properly.  If a program does not work with Python 2, the solution is to [https://docs.python.org/3/howto/pyporting.html port it to Python 3].
-Python 3 has been the default version of Python on our systems since early 2020.  We plan to completely remove Python 2 from our Linux clients sometime after the Fall 2020 semester.
+Python 3 has been the default version of Python on our systems since early 2020.  We expect to completely remove Python 2 from our Linux clients once even the legacy packaging is no longer officially supported by our Linux distributor.
 == Installing Python Packages ==

← Older revision		Revision as of 14:02, 7 July 2021
Line 1:		Line 1:
−	All of the CS Department's [[:Category:Linux Clients\|Linux clients]] have both Python 2.7 ~~and~~ Python 3 ~~installed~~. This page has some information about how Python works in our environment.	+	All of the CS Department's [[:Category:Linux Clients\|Linux clients]] have both Python 3 and Python 2.7 installed. The default version is Python 3. This page has some information about how Python works in our environment.

	You may also want to read about [[Python on the CS Webservers]].		You may also want to read about [[Python on the CS Webservers]].

@@ Line 7: / Line 7: @@
 Although Python 2.7 is installed on our systems, it should only be used when needed for compatibility with older programs.  Official support for Python 2 ended in January 2020.  New programs should use Python 3, and old Python 2 programs may not work properly.  If a program does not work with Python 2, the solution is to [https://docs.python.org/3/howto/pyporting.html port it to Python 3].
-We plan to completely remove Python 2 from our Linux clients sometime after the Fall 2020 semester.
+Python 3 has been the default version of Python on our systems since early 2020.  We plan to completely remove Python 2 from our Linux clients sometime after the Fall 2020 semester.
 == Installing Python Packages ==

@@ Line 5: / Line 5: @@
 == Note: Python 2 is Deprecated ==
-Although Python 2.7 is installed on our systems, it should only be used when needed for compatibility with older programs.  As of January 2020, official support for Python 2 has ended.  New programs should use Python 3, and old Python 2 programs may not work properly.  If a program does not work with Python 2, the solution is to [https://docs.python.org/3/howto/pyporting.html port it to Python 3].
+Although Python 2.7 is installed on our systems, it should only be used when needed for compatibility with older programs.  Official support for Python 2 ended in January 2020.  New programs should use Python 3, and old Python 2 programs may not work properly.  If a program does not work with Python 2, the solution is to [https://docs.python.org/3/howto/pyporting.html port it to Python 3].
-We plan to completely remove Python 2 from our Linux clients after the Fall 2020 semester.
+We plan to completely remove Python 2 from our Linux clients sometime after the Fall 2020 semester.
 == Note: Change in Default Python Version ==

← Older revision		Revision as of 13:27, 13 April 2020
Line 66:		Line 66:

	[[Category:Linux Clients]]		[[Category:Linux Clients]]
−	[[Category:Software]]	+	[[Category:Software Available On The CS Linux Clients]]

@@ Line 11: / Line 11: @@
 == Note: Change in Default Python Version ==
-In January 2020, we upgraded our Linux clients from Fedora 29 to Fedora 31.  On our now-upgraded Fedora 31 systems, the <code>python</code> program is Python ''3.7''.  If you need to, you can use <code>python2</code> to get Python 2.7.  (You can also use <code>python3</code> to get Python 3.)  The change in the default Python version may cause existing programs to break if they don't specify which Python version they want.  You should explicitly name the Python your program expects by starting it with either:
+In January 2020, we upgraded our Linux clients from Fedora 29 to Fedora 31.  On our now-upgraded Fedora 31 systems, the <code>python</code> program is ''Python 3.7''.  If you need to, you can use <code>python2</code> to get Python 2.7.  (You can also use <code>python3</code> to get Python 3.)  The change in the default Python version may cause existing programs to break if they don't specify which Python version they want.  You should explicitly name the Python your program expects by starting it with either:
   #!/usr/bin/env python3

@@ Line 47: / Line 47: @@
   virtualenv ~/python/project-1
-To start using the virtual environment, you must use one of the "activate" scripts in the environment's "<code>bin</code>" directory.  If your login shell is bash or zsh, use <code>activate</code> .  If you're using csh or tcsh, use <code>activate.csh</code> .  (See "[[Shells Available for CS Accounts (bash, tcsh, etc.)#How to Tell What Shell You.27re Using|How to Tell What Shell You're Using]] if you're not sure what your shell is.)  Load the appropriate script with the <code>source</code> command:
+To start using the virtual environment, you must use one of the "activate" scripts in the environment's "<code>bin</code>" directory.  If your login shell is bash or zsh, use <code>activate</code> .  If you're using csh or tcsh, use <code>activate.csh</code> .  (See [[Shells Available for CS Accounts (bash, tcsh, etc.)#How to Tell What Shell You.27re Using|How to Tell What Shell You're Using]] if you're not sure what your shell is.)  Load the appropriate script with the <code>source</code> command:
   source ~/python/project-1/bin/activate

@@ Line 1: / Line 1: @@
 All of the CS Department's [[:Category:Linux Clients|Linux clients]] have both Python 2.7 and Python 3 installed.  This page has some information about how Python works in our environment.
 == Installing Python Packages ==
-We try to have a good selection of the most-commonly-useful Python packages preinstalled on the Linux clients and available for both Python 2 and 3.  It sometimes happens that people need one or more packages that aren't currently installed.  Here's how you can get the packages you need.
+We try to have a good selection of the most-commonly-useful Python packages preinstalled on the Linux clients.  It sometimes happens that people need one or more packages that aren't currently installed.  Here's how you can get the packages you need.
 === pip ===
-<tt>pip</tt> is installed on our systems, so if you need a package (and if it's in the Python Package Index), you can install it for your own personal use with:
+<code>pip</code> is installed on our systems, so if you need a package (and if it's in the Python Package Index), you can install it for your own personal use with:
   pip install --user ''package''
-For Python3, use <tt>pip3</tt> instead of <tt>pip</tt>.
+If you need a Python 2 package, use <code>pip2</code> instead of <code>pip</code>.
 Note that, for ugrad accounts, the package will count against your [[Disk Quotas|disk quota]].
@@ Line 19: / Line 37: @@
   pip uninstall ''package''
-<tt>pip</tt> will figure out on its own that it was locally-installed.
+<code>pip</code> will figure out on its own that it was locally-installed.
 === virtualenv ===
-For complete control over what Python packages are available, you can use [https://virtualenv.pypa.io/en/stable/ virtualenv].  It uses a directory to hold a complete set of packages that are entirely independent from whatever is installed in the system (or in your home directory via <tt>pip install --user</tt>).
+For complete control over what Python packages are available, you can use [https://virtualenv.pypa.io/en/stable/ virtualenv].  It uses a directory to hold a complete set of packages that are entirely independent from whatever is installed in the system (or in your home directory via <code>pip install --user</code>).
-To use a virtual environment, pick a directory where it will keep its data and use the <tt>virtualenv</tt> program to initialize the directory.  For example, if you want to make a "project-1" environment and keep all of your environments in a "~/python" directory, you could do this:
+To use a virtual environment, pick a directory where it will keep its data and use the <code>virtualenv</code> program to initialize the directory.  For example, if you want to make a "project-1" environment and keep all of your environments in a "~/python" directory, you could do this:
   virtualenv ~/python/project-1
-To start using the virtual environment, you must use one of the "activate" scripts in the environment's "<tt>bin</tt>" directory.  If you haven't changed your shell on our systems, use <tt>activate.csh</tt> .  If you're using bash, use <tt>activate</tt> .  Load the appropriate script with the <tt>source</tt> command:
+To start using the virtual environment, you must use one of the "activate" scripts in the environment's "<code>bin</code>" directory.  If your login shell is bash or zsh, use <code>activate</code> .  If you're using csh or tcsh, use <code>activate.csh</code> .  (See "[[Shells Available for CS Accounts (bash, tcsh, etc.)#How to Tell What Shell You.27re Using|How to Tell What Shell You're Using]] if you're not sure what your shell is.)  Load the appropriate script with the <code>source</code> command:
-  source ~/python/project-1/bin/activate.csh
+  source ~/python/project-1/bin/activate
-Your shell prompt will change to show the environment you're using.  No packages will be available to start with, but you can install them with "<tt>pip install ''package''</tt>" (without the "<tt>--user</tt>" parameter).
+Your shell prompt will change to show the environment you're using.  No packages will be available to start with, but you can install them with "<code>pip install ''package''</code>" (without the "<code>--user</code>" parameter).
-To leave the virtual environment, simply use the <tt>deactivate</tt> command:
+To leave the virtual environment, simply use the <code>deactivate</code> command:
   deactivate