|
|
|
|
|
|
by worik
844 days ago
|
|
|
I have said two examples: mod-ui: https://github.com/moddevices/mod-ui/issues/145#issue-203423... and Yocto, no link for that. Installing multiple versions of Python? You have got to be kidding. But I did try that. I cannot remember the details, all I remember was the inability (a software hellscape) to get a system that had to be built with one version of Python to play well with a package that had to be built with a later version. It is 2024, what have they learnt? Just keep backward compatibility, it is not that hard. |
|
|
Why? There's some overhead because it's not like everything has changed between versions, but otherwise it's a very clean way to provide exactly what you need without having to maintain backwards compatibility in future development.
Mind, as long the the Python code you're running _isn't_ using removed or significantly changed function, you can absolutely run code written for Python 3.6 with the 3.8 interpreter, and so on. If I recall correctly, this is _why_ it's uncommon to specify maximum versions in Python packages: unless it is specifically incompatible with a change in a newer version it should generally be assumed to work, and pinning a maximum version would just cause it to fail for no reason.
In your Issue with mod-ui, they specifically say
> mod-ui is not compatible with python3.11, so this wont work.
but your second attempt is still using 3.11 based on your output. It's a shame this isn't better documented since it seems to be known, but that seems like an issue with the project, not Python?