Pipenv tries to do so much (e.g. a pipenv command involve poking around procfs to detect shell via shellingham to display colors), used to introduce breaking changes between releases (before they switched the scheme to CalVer), and takes a really long time between each releases (longer for bugs to get fixed).

Most people that switched from Pipenv to Poetry were probably done so during the end of 2018 throughout 2019, of which Pipenv has no releases at all[1] (non-alpha/beta version were only released in November 2018 then May 2020).

There were a rant from few years ago[2][3] regarding other issues (performance, etc.).

[1]: https://news.ycombinator.com/item?id=21781421

[2]: https://chriswarrick.com/blog/2018/07/17/pipenv-promises-a-l...

[3]: https://news.ycombinator.com/item?id=18612590

Pip-tools was around a lot longer (more than two years).

It kind of works for my team, but only because nobody touches it anymore.

What's so bad about it? Well it's bad at being package manager for starter. Here is a quick question. How do you install packages with pipenv with the versions specified in the lock file?