<story><title>Pipenv: promises a lot, delivers very little</title><url>https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-lot-delivers-very-little/</url></story><parent_chain><item><author>greysteil</author><text>Sometimes, improvements don&amp;#x27;t happen in a straight line.&lt;p&gt;There&amp;#x27;s been a lot of work on Pipenv over the the last 6 months, predominantly by Dan Ryan and Tzu-Ping Chung, and it&amp;#x27;s getting stronger and stronger with each release.&lt;p&gt;If you&amp;#x27;ve gone back to using pip I&amp;#x27;d encourage you to give Pipenv another try. Introducing a lockfile is a big step forward for Python dependency management, and the team working on Pipenv are committed and doing a great job.</text></item><item><author>legostormtroopr</author><text>Pipenv is a really interesting development for Python, and I&amp;#x27;m glad that someone was working to improve dependency locking for Python.&lt;p&gt;However, Kenneth abused his position with PyPA (and quickly bumped a what is a beta product to version 18) to imply Pipenv was more stable, more supported and more official than it really was.&lt;p&gt;And worse still, for anyone saying &amp;quot;but ts open source, you get what you pay for&amp;quot;, Kenneth as former Python Overlord at Heroku, encouraged Heroku to place Pipenv above Pip as the default Python package manager in the Python buildpack. This decision impacted paying customers and the Python buildpack used a broken version of Pipenv for a long time. So long, most people I know just went back to Pip.&lt;p&gt;Then, lastly, when people complained he had a tizzy at reddit and twitter and got PyPA to help backtrack and say &amp;quot;no we didn&amp;#x27;t support it, nope, its just a thing that happened&amp;quot;, all while the main Pipenv Github repository was held under the PyPA GitHub Org.</text></item></parent_chain><comment><author>legostormtroopr</author><text>&amp;gt; Sometimes, improvements don&amp;#x27;t happen in a straight line.&lt;p&gt;I don&amp;#x27;t deny that, what I am (and the article is) saying is that we were sold on Pipenv being &amp;quot;the officially recommended Python packaging tool from Python.org&amp;quot;.&lt;p&gt;And PyPA didn&amp;#x27;t refute it, and Heroku didn&amp;#x27;t refute it, so the community bought it.&lt;p&gt;Yes, introducing a Lockfile is huge, and it was massively needed, and thats why when we were told &amp;quot;heres the official way to do it&amp;quot;, we got excited. Then we got daily breaking updates, rude issue close messages, and a giant backtrack of &amp;quot;its free and still under development, why do you expect so much from us?&amp;quot;</text></comment>
<story><title>Pipenv: promises a lot, delivers very little</title><url>https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-lot-delivers-very-little/</url></story><parent_chain><item><author>greysteil</author><text>Sometimes, improvements don&amp;#x27;t happen in a straight line.&lt;p&gt;There&amp;#x27;s been a lot of work on Pipenv over the the last 6 months, predominantly by Dan Ryan and Tzu-Ping Chung, and it&amp;#x27;s getting stronger and stronger with each release.&lt;p&gt;If you&amp;#x27;ve gone back to using pip I&amp;#x27;d encourage you to give Pipenv another try. Introducing a lockfile is a big step forward for Python dependency management, and the team working on Pipenv are committed and doing a great job.</text></item><item><author>legostormtroopr</author><text>Pipenv is a really interesting development for Python, and I&amp;#x27;m glad that someone was working to improve dependency locking for Python.&lt;p&gt;However, Kenneth abused his position with PyPA (and quickly bumped a what is a beta product to version 18) to imply Pipenv was more stable, more supported and more official than it really was.&lt;p&gt;And worse still, for anyone saying &amp;quot;but ts open source, you get what you pay for&amp;quot;, Kenneth as former Python Overlord at Heroku, encouraged Heroku to place Pipenv above Pip as the default Python package manager in the Python buildpack. This decision impacted paying customers and the Python buildpack used a broken version of Pipenv for a long time. So long, most people I know just went back to Pip.&lt;p&gt;Then, lastly, when people complained he had a tizzy at reddit and twitter and got PyPA to help backtrack and say &amp;quot;no we didn&amp;#x27;t support it, nope, its just a thing that happened&amp;quot;, all while the main Pipenv Github repository was held under the PyPA GitHub Org.</text></item></parent_chain><comment><author>rendaw</author><text>Pipenv tries to upgrade all the versions of everything in your lockfile whenever you add a new package (not just dependencies of the package), and there&amp;#x27;s no way to disable this behavior. Right now. That&amp;#x27;s the tip of the iceberg.</text></comment>