-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkg_resources should be a separately-distributed package #863
Comments
It's a good idea, but not immediately feasible due to bootstrapping issues. |
You mean, there's a bit of a chicken-and-egg problem? |
Yes. The issue that #581 seeks to address. |
Any update on this issue? Our library depends on |
pkg_resources should present its own package, but it's difficult to do. I don't even know it's feasible, but I'm working on it in pypa/pkg_resources and the feature/vendor-pkg-resources branch of setuptools. |
Since PyCon 2018, I've been focusing on the importlib_metadata project. This work might still proceed, but it's less important if importlib_metadata can largely obviate the need for pkg_resources. |
The pkg_resources module provides some functionality which is need during the "runtime" of a package, while setuptools' functionality is only required during the build. For not having to depend on the full setuptools egg, it would be good to provide an pkg_resources egg which packages can depend on.
The text was updated successfully, but these errors were encountered: