Some components may still have a dependency on Py2. Check for that.
Some folks (cough) have been known to create an alias, so any arcane component that wants py2 will be pointed to / serviced by py3. Test first, before moving forward.
Do you actively use Py yourself? Or did you make this discovery purely by accident ?
$ which python
which: no python in $PATH
$ which python3
/usr/bin/python3
I did a fresh install about a 5 6 weeks ago and I did actively clean up python310* packages using zypper as I saw a mix of python310 and python311 likely because I did install some python310* I use and that are not part of the default install.
I did the same cleanup an hour ago with both my primary and secondary desktops. ( not a reinstall, but cleanup of py stuff).
Shocked at how many duplicates there were for py310 and py311.
Basically, I did a …
zypper remove --dry-run python310*
… first to test for potential side effects. No prob, so ran it for real. Did this on the secondary machine, rebooted, tested, etc… then jumped to the primary and did the same there.
.
.
I also checked for “package conflict” for any rogue packages in Packman… only a couple that were satisfied in a standard repo … so was finally able to remove any dependency on Packy.
Hello, this is Gulshan Negi
Well, if you want to transition to Python 3.x and utilize the latest Python libraries, you can follow the steps outlined below:
Install Python 3 using the package manager.
Establish a virtual climate utilizing the venv module to segregate your Python projects.
To use Python 3, activate the virtual environment.
Introduce Python libraries utilizing pip inside the virtual climate.
Make changes to any applications or scripts so that they use Python 3 in the shebang line.
Make sure your code is compatible with Python 3 by testing and migrating it.