Explore multiple Python installs

[emtuls]

Details

Currently, we restrict ourselves to Python 3.10 due to certain package requirements, which is fairly limiting at times.

I think some exploration into having multiple python installs would be worthwhile. I did a quick check and it seems like most of our python libraries we install support up to at least 3.13 (most seem to do 3.14, with one notable exception of pythonnet only working with < 3.13), with a couple (stringsifter and unpy2exe) requiring 3.11 at the latest.

I'm thinking of moving python3.vm to being version 3.13, and splitting stringsifter and unpy2exe into their own individual tools, with requirements of python 3.11 for both.

This seems to make sense anyway, due to these tools not being importable libraries anyway, as they are both used from the command line (we already do this for uncompyle6 and unpyc3 for example). We would add shortcuts to the Python section which runs these tools with the required python version, for example py -3.11 -m unpyc3

This also opens the door for other tools which require higher python versions to even be installed, and some like pylingual (https://github.com/syssec-utd/pylingual) which work better when multiple versions are installed.

On another note, 2 python packages seem to not be working at all:

• binwalk doesn't work and should be removed in favor of the newer Rust implementation: https://github.com/ReFirmLabs/binwalk.
• unpy2exe doesn't seem to actually be working and has long been unmaintained and I think we should remove it.

[emtuls]

With pymanager being the future of python installs. I think we should consider using it as our primary source of installing python and handling multiple versions.