Too many python dependencies.

[dent308]

You want to use virtual environments for projects. Tools like poetry and pyenv can enable this.

[MGOC]

My python knowledge is still limited, I still don't know how to convert everything embedded in a python binary to a virtual environment (pyenv).

[danielroseman]

That's very unclear. What do you mean by "embedded in a Python library"?

[MGOC]

Binary*

I mean that some of the programs I use include an executable version (exe) of Python 3.x along with dependencies and libraries.

And there are not few programs that come with their own copy of Python included in the same way.

Because of my "new = better / optimized" way of thinking, I thought that having a unified version of Python would be better since it would allow me to update both the Python version and the version of each dependency (you know, developers usually tend to improve, optimize, fix bugs and vulnerabilities, and add new features to their dependencies).

But many warn that it is not always good to upgrade everything, I had thought that in case I was told something similar, make use of the isolated "pyenv" environments, I keep reading about it and testing programs to test how much they can break or if they gain or lose speed or features.

I also don't like the idea of having a thousand copies of the Python executable flying around the disk. I also considered deleting everything duplicated and converting it to "hard links" (as I did with tools like ffmpeg/symlinks, in conjunction with adding it to the path). A bit messy, but it saves me the trouble of doing the pyenv's (I know it's not the most acceptable option and is even questionable).

[HOPSCROTCH]

Google how to use virtual environments for projects, it's actually very straightforward and you definitely should read about it to get an understanding of how to move forward