Jesus Michał "Le Sigh" 🏔 (he)#Python is just doing great. We're not having impossible constraints, as some projects need old #setuptools for pkg_resources, and other projects are starting to require newer setuptools for some fancy new features. And ofc after promising to release pkg_resources standalone over a month ago, setuptools upstream didn't deliver.
Clément Robert@mgorny looks like everyone wants this package and nobody wants to maintain it.
@neutrinoceros, I wouldn't say that's accurate. More like, nobody wants to step out of the line when setuptools maintainers clearly have the right for the name and indicated they'll do it.
@mgorny you’re right. Though I’m curious what parts of pkg_resources are actually used that don’t have a replacement already. Do you have any pointers for that ?
@neutrinoceros, the problem is not lack of a replacement. The problem is that they're used by a package that is dead and buried for 5 years already, but everyone refuses to acknowledge that and move on.
@mgorny “dead and buried”: you pkg_resources itself, or its dependees ?
@neutrinoceros, packages that require pkg_resources. For example, passlib.
@mgorny no way. People rely on a security critical piece of software that’s been unmaintained for half a decade??