Re:Pipenv: promises a lot, delivers very little
by sweatersong on Wednesday December 05, 2018 @05:01PM
(#18613075)
I'm looking into transitioning to poetry from Pipenv...my main gripes with Pipenv are 1) pyenv integration is cludgey and 2) "hard" conflicts between packages are unresolveable in pipenv and means you cannot lock your environment.
As far as #2 is concerned, does poetry allow you "ignore" or change subdependency requirements for specific packages a la maven?
As far as #2 is concerned, does poetry allow you "ignore" or change subdependency requirements for specific packages a la maven?