4 ms·

If appA needs python3.6 then call it with `python3.6` not `python3`. It can exist in your /usr/bin in parallel with 3.7. The standard python used by your distri

• wuxiekeji 6y ago
  What if an app needs python 3.3, 3.4, 3.5, or 3.6? This is why we have semantic versioning. An app should be able to say it wants "python3>=3.3" with the expectation that any version 3.3 or later should not break its code. Requiring specifically 3.6 would mean that the user inevitably has to install every version of 3.x at the same time to satisfy all the apps, along with "dist-packages" directory containing every library for every version of 3.x, and that would be a complete mess. > It can exist in your /usr/bin in parallel with 3.7 Also, no. Installing python3=3.7 with apt will remove 3.8 and break or auto-uninstall all your python apps that actually want 3.8. Sure, you can compile and install from scratch and have both coexist but that just breaks what everyone is arguing for in this thread (good dependency management without containerization). But when the folks who package python don't cooperate, containerization is actually a really good workaround for this.