4 ms·
Pipenv solves a very real problem, but it has a lot of problems of its own: - It's very slow: re-locking after updating 1 dependency often takes me ~1 minute.
by alexbecker 8y ago
Pipenv solves a very real problem, but it has a lot of problems of its own:
- It's very slow: re-locking after updating 1 dependency often takes me ~1 minute.
- It has lots of bugs. To name a few in 11.6.9: clobbers comments in the Pipfile, inconsistently includes dependencies for other build environments in Pipfile.lock, stores the wrong index in Pipfile.lock for packages not on PyPI.
- They release multiple times per day, often breaking things in patch releases.
- Kenneth Reitz is quite unpleasant to deal with in GitHub issues, which I often have to because of the previous 2 issues.
From what I've heard, Pipenv "has been officially blessed" only insofar as its maintainer got commit access to PyPA's documentation and inserted a recommendation.
- dvnguyen 8y agoIf what you've heard is true, it could be pretty toxic. Do you have any evidences to back up?
- jwilk 8y agoThe recommendation was added by Jon Wayne Parrott: https://github.com/pypa/python-packaging-user-guide/pull/443 https://github.com/pypa/python-packaging-user-guide/pull/443 He doesn't seem to be a pipenv maintainer: https://github.com/pypa/pipenv/commits?author=jonparrott https://github.com/pypa/pipenv/commits?author=jonparrott
- kennethreitz 8y agoI apologize for not meeting perfect standards of mood at all times. I have bipolar disorder, for what it's worth, and working on a packaging tool is very stress-inducing.
- divbzero 8y agoIt’s not easy to develop for large communities, and even tougher to speak frankly about oneself. Keep up the good work.
- kennethreitz 8y agoAlso: > From what I've heard, Pipenv "has been officially blessed" only insofar as its maintainer got commit access to PyPA's documentation and inserted a recommendation. This is blatantly false.