3 ms·
Pipenv has felt to me like a pretty solid solution. It's not perfect but it's a lot better than the other options.
by sosodev 7y ago
Pipenv has felt to me like a pretty solid solution. It's not perfect but it's a lot better than the other options.
- j88439h84 7y agoIt is not as good as Poetry.
- Chris2048 7y agofrom poetry docs: https://github.com/sdispater/poetry/blob/master/README.md#dependency-resolution https://github.com/sdispater/poetry/blob/master/README.md#de... " Let's take an example: pipenv install oslo.utils==1.4.0 will fail with this error: Could not find a version that matches pbr!=0.7,!=2.1.0,<1.0,>=0.6,>=2.0.0 while Poetry will get you the right set of packages "
- yrro 7y agoLast time I gave it a go, I found it was pretty strongly welded to virtualenv, rather than using Python's own (much less problematic) venv. I came away less than enthused as a result. (To be fair, modifying it to use venv is... non-trivial).
- 89qh4p 7y agoPipenv has a good approach to management, similar to npm, but the implementation is buggy. It gained popularity by being recommended very early on in the official python documentation while being misleadingly advertised as production-ready. If you look at the issues section in its github repo, you'll see that there are some pretty basic bugs there which are very annoying or disruptive. Moreover it seems the author has almost left the boat and a handful of contributors have to tidy things up. Just to illustrate my point. I think a package manager that takes a few minutes to install a single tiny package, or don't prevent you from adding non-existing packages (e.g. spelling mistake), or doesn't let you install a new package without trying to upgrade all other packages isn't really production-ready. These are known issues since November last year.