Python-Environments.md

@@ -11,6 +11,8 @@ The advantage of _2_ is that a limited number of custom environments may be shar
 
 The Jaynes research group is just beginning to use option _2_ with tentative success.  A group-wide `bashrc` defines a command `activate` which finds the appropriate `venv` environment in a group shared directory.
 
+Another problem is with the newest version of Python supported on each platform.  (By "supported", I mean available through the standard system software maintenance utilities.)  For example, the newest supported Python version on the Rocky 8 servers is 3.9, while, currently, the newest supported version on the Rocky 9 systems is 3.12.  This means that if your application requires something above 3.9, then you will have to login to one of the Rocky 9 systems explicitly.
+
 Note that I'm (@ljg) no Python expert, so please feel free to join the [discussion](https://research-git.uiowa.edu/space-physics/doc/-/issues/6) on this topic or directly fix this Wiki page.
 
 ## User-based Individual Configuration
@@ -28,3 +30,5 @@ pip3 install --user
 ### venv
 
 ## Research-group Shared Configuration
+
+The initial experiments being implemented for the Jaynes research group involve a Bash function defined in a group shared `bashrc` that defines an `activate` command which looks for available `venv` environments stored in a shared location.  See the [discussion](https://research-git.uiowa.edu/space-physics/doc/-/issues/6) for details.  Currently, the command `activate aurorax` sets up the group shared environment for working with pyaurorax.