Extract package_index as third-party package #2110
Comments
|
I am not sure how long I plan to look if the dependency on |
|
Nevertheless, if extracting |
|
This issue is obsolete. Setuptools 80 removed easy_install and package_index (although the package_index removal didn't happen until 80.3 or so). In #4983, I'm considering a deprecation process for package_index to provide a smoother transition. |
|
buildout still uses |
In #2089, @gotcha indicates that
zc.buildoutis usingsetuptools.package_indexthrough its API. At the same time,setuptoolsis working to reduce its scope of responsibility to mainly being a PEP 517 package builder.I took a quick look at pip and its package index functionality is tucked carefully inside
_internal.To support use-cases like
zc.buildoutand other libraries that wish to interact programmatically with the package index, and to separate that functionality from setuptools' primary mission, perhapssetuptools.package_indexshould become a package in its own right. To avoid forking the behavior, setuptools could vendor an initial, compatible release.Oh, there is already something called package-index which purports to do some of the things that setuptools' module does. That's too bad, because I'm all but certain that module won't be compatible with what setuptools needs or even what zc.buildout needs.
It looks like @mdrachuk created that package last year and hasn't yet made a non-pre-release. Misha, is that package in active use? How would you feel about merging our efforts and supporting a package that (at least initially) supports the setuptools.package_index API, but ultimately has the features/designs you require?
The text was updated successfully, but these errors were encountered: