Python new version

The Python Landscape: A Quick Overview Understanding Python Versioning Stability vs. New Features Long-Term Support (LTS) Versions Compatibility Concerns The Role of Virtual Environments When Should You Upgrade? Testing Across Versions Wrapping It Up FAQs Conclusion You might also read:So, you're diving into the world of Python, huh? And now you're faced with the question: which version of Python should you use? It's a good question! Python has been around since 1991, and over the years there have been quite a few versions released—each with its own features, quirks, and advantages. In this post, I’ll figure things out as I go along and share what I’ve learned about selecting the right Python version for your project.The Python Landscape: A Quick OverviewFirst off, the most notable versions you’ll encounter are Python 2 and Python 3. Python 2 reached the end of its life in January 2020, which means it’s no longer officially supported. This is significant because no updates, not even security fixes, will be provided. So if you’re picking a version today, Python 3 is the clear choice, right? But then I think, there's more to it! What about the specific versions within Python 3?Understanding Python VersioningPython follows a versioning system like many programming languages: major, minor, and patch. For example, in Python 3.10.0:3 is the major version10 is the minor version0 is the patch versionSo, every time a new major version is released, there are major changes. Minor versions introduce new features, while patches usually fix bugs. It’s kinda confusing at first—like, how do I know if I should jump on the latest version right away, or wait until things stabilize a bit?Stability vs. New FeaturesOkay, let’s explore this further. Suppose you need the latest features. For instance, Python 3.11 introduced some cool optimizations and features like new syntax for error handling and performance improvements. But then you think about stability. If you're working on a production application, there’s something to be said for sticking with a version that’s been around for a while. Python 3.9, for example, is widely regarded as stable and has extensive community support.Long-Term Support

The Python Releases for Mac OS X page and download the latest stable release macOS 64-bit/32-bit installer.After the download is complete, run the installer and click through the setup steps leaving all the pre-selected installation defaults.Once complete, we can check that Python was installed correctly by opening a Terminal and entering the command python3 --version. The Python 3.13.0 version number should print to the Terminal.Note: This version will change as new releases come out.Advanced Since our system now has both Python 2 (which came pre-installed) and Python 3, we must remember to use the python3 command (instead of just python) when running scripts. If you would rather not have to remember the python3 command and just use python instead, then creating a command alias is your best bet.Execute open ~/.bash_profile from a Terminal (if the file was not found, then run touch ~/.bash_profile first).Copy and paste alias python="python3" into the now open .bash_profile file and save.While we’re at it, go ahead and copy and paste alias pip="pip3" into the file as well in order to create an alias for the Python 3 pip package manager.Finally, restart the Terminal and run python --version. We should see the exact same output as running python3 --version.WindowsFollow the below steps to install Python 3 on Windows.Go to the Python Releases for Windows page and download the latest stable release Windows x86-64 executable installer.After the download is complete, run the installer.On the first page of the installer, be sure to select the “Add Python to PATH” option and click through the remaining setup steps leaving all the pre-select installation defaults.Once complete, we can check that Python was installed correctly by opening a Command Prompt (CMD or PowerShell) and entering the command python --version. The Python 3.13.0 version number should print to the console.Note: This version will change as new releases come out.Installing MinicondaMacFollow the below instructions to install the latest Miniconda version for Mac.Go to the Miniconda Download page and download the Python 3.13.0 Mac OS X 64-bit .pkg installer.Note: This version will change as new releases come out.After the download is complete, run the installer and click through the setup steps leaving all the pre-selected installation defaults.Once complete, we can check that Miniconda was installed correctly by opening a Terminal and entering the command conda list. This will print a list of packages installed by Miniconda.WindowsFollow the below instructions to install the latest Miniconda version for Windows.Go to the Miniconda Download page and download the Python 3.13.0 Windows 64-bit .exe installer.Note: This version will change as new releases come out.After the download is complete, run the installer and click through the setup steps leaving all the pre-selected installation defaults.Once complete, we can check that

Sudo pip3 freezeConfirm versions of Python and Pip on the NEW Matillion ETL instance.SSH on to the Matillion instanceRun the following commands and compare the output against the CURRENT Matillion ETL instance. The NEW Matillion ETL instance should be of the same or later version of Python2/3 as the CURRENT Matillion ETL instance.Python2 sudo python --versionPython2 sudo pip --versionPython3 sudo python3 --versionPython3 sudo pip3 --versionConfirm the Python Libraries installed and the version of each on the NEW Matillion ETL instance.SSH on to the Matillion instanceRun the following commands and note the output. Note that by default, a new Matillion instance will have some Python libraries installed.Python2 Libraries: sudo pip freezePython3 Libraries: sudo pip3 freezeCompare the list of Python Libraries on the CURRENT Matillion instance against the list of Python Libraries on the NEW Matillion instance. Based on the comparison, identify the Python libraries that need to be installed on the new instance.Install each Python library that is required on the NEW Matillion instance, ensuring to install the exact same version of the library installed on the CURRENT Matillion instance.Python2 - Install a library of a specific version:sudo pip install [modulename]==[version number]Example: sudo pip install boto3==1.14.53Python3 - Install a library of a specific version:sudo pip3 install [modulename]==[version number]Example: sudo pip3 install boto3=1.17.45Advanced TopicsThe topics below focus on "advanced topics" related to using Python with Matillion ETL. Many of the sections below link to other documentation topics.Disabling Python on a Matillion ETL instanceIt is possible to disable the Python Script feature on a Matillion instance. Following are the steps to do so:SSH on to the Matillion instanceMake a backup of a configuration file that will be edited:sudo cp /usr/share/emerald/WEB-INF/classes/Emerald.properties /usr/share/emerald/WEB-INF/classes/Emerald.properties.backupEdit the same configuration file:File: /usr/share/emerald/WEB-INF/classes/Emerald.propertiesAdd the following to the end of the file: ALLOW_PYTHON_COMPONENTS=falseRestart the Matillion service.From an SSH session:sudo service tomcat stopsudo service tomcat startFrom a Matillion UI session:Click Admin → Restart ServerRestricted UsersBy default, when a Python Script component executes, it runs as an external process on the Matillion ETL server directly, with the same privileges as the web server. It is possible to restrict the execution of the Python