31–40 of 325 posts
Pipenv has spawned so much controvery.. One big shitfest. Python packaging in general is such a messy ecosystem
> Python packaging in general is such a messy ecosystem Not just messy. It’s probably worst in class. I at least can’t come up with a single worse package-management story which I do know of. Edit: I’m talking about platforms with actual package-management which sucks, not platforms with the absence of package-management all together.
Pipenv has spawned so much controvery.. One big shitfest. Python packaging in general is such a messy ecosystem
> Python packaging in general is such a messy ecosystem Not just messy. It’s probably worst in class. I at least can’t come up with a single worse package-management story which I do know of. Edit: I’m talking about platforms with actual package-management which sucks, not platforms with the absence of package-management all together.
669 commits in the last year... and asking if the project is dead? I'm a bit confused here. Maybe the project is mismanaged, or there's some upstream issue with package distro, but it seems to be far from dead.
This is all MIT licensed, if people care so much, why has nobody forked this? Why are people talking about jumping ship to a completely different project instead of forking and cutting a new release from there?
It does seem dead. The dead don’t speak. And no one is replying to this question.
That way the barrier for moving to a diffident fork would be lowered.
> I'm not mad, I don't think you're bad people, but the least y'all can do is be honest with us how entitled can someone be, you have the source code, if you're not happy why not contributing yourself? It is like some people don't realize most of these projects are other people working for free on their free time and giving that for free to anyone that feels like using it
How would you feel if your fixed the bug patch more than two years ago, your PR was accepted.. but users still do not have the fix?
Why would someone choose to use a third party library when the first party solution[0] is more than adequate in the first place? [0] https://docs.python.org/3/library/venv.html
1. Because pipenv is easier to use. 2. Because it's not at all clear that pipenv is a third party library. It's made by the same group that makes pip, so it's confusing that pip would be considered a de-facto standard but not pipenv when it's made by the same group, and under the same project in Github.
If there are no commits, maybe that means it is finished, stable, reliable? I would like more projects to be without commits and just work. I don't understand why there must always be new commits if everything already works.
This project has 313 open issues. No, everything’s does not already work.