I also found it's insistence on doing certain things reduced my flexibility. We thought it was kind of dead for a while where there were no releases for about a year.
That said, I've generally found a rise in opinionated tooling (see: black) and that frustrated me for a while. Then i realised i can just ignore it all and still be productive with my old stack if i knew what i was doing (which i do) while people still blurt their opinions elsewhere.
It certainly was dead in that time
Can you elaborate on this? I use pip-compile development.in and pip-compile production.in and both use -r base.in for shared dependencies
pip-compile production.in
then use the pinned production requirements and a dev.in to produce the dev environment.
Key point being that the dev environment needs to have the very same pinned versions for all packages that are part of the prod environment.
It supports as many separate requirements files as you want, if that's what you mean.
For one, I think competition, there is Kenneth Reitz' pipenv and then of course conda's environment.yml. I think pipenv lost the popularity contest but somehow lead to a situation where people wondered on which horse to bet.
Conda also takes a lot of market share esp. in the machine-learning deployments while also being not a 'perfect' tool.
Pretty sure we will see more poetry in the coming years.
Last but not least Poetry sometimes also feels like a weird tool. For example, when its dumping colourful stack traces on you in case of (invalid) inputs, etc.
If pip-compile would support dev and production requirements it would still be my way to go I think.