Re:Pipenv: Python Dev Workflow for Humans
by gjvc on Wednesday February 03, 2021 @05:26PM
(#26020021)
Agree. Works fine for me exactly as you describe. I don't understand why people furiously want more than this for the common case. (Choose python version, create .venv/ directory, install packages, use installed .venv/ and do work.)
[ Parent
| on HN ]
Re:Pipenv: Python Dev Workflow for Humans
by lazypenguin on Wednesday February 03, 2021 @05:46PM
(#26020235)
What happens when you use a different version of the same library that a dependency uses?
Re:Pipenv: Python Dev Workflow for Humans
by CrLf on Wednesday February 03, 2021 @07:01PM
(#26020910)
Sometimes it works, sometimes it doesn't. This is indeed a problem, but one for which there isn't an elegant solution.
When multiple versions of the same library are allowed to coexist in different dependency trees there is less incentive to solve these conflicts and versions proliferate (see npm).
I'd much rather solve the occasional conflict (usually solved either by settling on some older version of both parent dependencies - and later advancing as possible - or just trying to fix it and send a patch upstream).