| > what I (and probably most of us virtualenv users) are saying is that there's a pretty broad swathe of projects where you don't encounter them. Zero. The required number of problems needs to be zero - hence my OP > I guess if you have a hard dependency on a particular version of python, it's going to be harder, but... why? The bigger question is - why doesn't 3.9 compile and run 3.8 Further, in what world is targeting a specific runtime version in an enterprise production environment "niche"? When you are deploying to managed corporate infrastructure, AWS Lambda runtimes, or strict Docker base images, you don't just get to loosely target "whatever Python version happens to be on the developer's laptop." You target an exact runtime version (e.g., Python 3.10) because language syntax, standard library features, and performance characteristics change between minor releases. The fact that Python forces the developer to manually manage isolated directory symlinks (venvs) just to prevent local environment contamination — and that minor runtime mismatches can completely derail a standard onboarding experience — is a structural UX failure. |
This is unrealistic. You seem to have moved to Go as an alternative, but I know because I've seen the complaints that Go doesn't satisfy that standard either.