I have wasted far too much time wrangling pythons packaging systems. Incompatibilities between pip, setuputils, distutils, virtualenv, eggs, C modules, and wheels I have literally given up. I love and use python but I no longer package it and deploy it for others to consume. Try to package a protobuf3/grpc system these days into a .deb, its a nightmare. Even the grpcio devs use docker containers to build packages because python has such a nightmare of a system.
I'll leave the second reason out for the sake of context
It's not the first time I say this, but I think it's crazy how long some package ecosystems live without a "sane" package manager, and how recently those even appeared.
pipenv --python python34Is that recent ?
Probably 7.0.0 or 3.2.9, where current version is 8.2.6: https://github.com/kennethreitz/pipenv/blob/master/HISTORY.t...
Also, I guess --python 3.4 would be the preferred way to do it, seems to work with either versions or executables.
https://docs.pipenv.org/basics.html#specifying-versions-of-p...
[1]: You put the third party code in /usr/local/lib/pythonX.Y/site-packages.
We knew[1] it was wrong in the 1990s, but /usr/local is a "best practice", and these people who believe "best practices" are more important than solid engineering breed faster.
Camacho for president 2020.