-
Notifications
You must be signed in to change notification settings - Fork 71
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
setuptools version limit #333
Comments
frenzymadness wrote at 2024-10-27 12:34 -0700:
What is the reason to limit the version of setuptools to:
https://github.com/zopefoundation/zope.interface/blob/7e0be48d15c594cc592537da2da98311017b19ab/pyproject.toml#L6
It seems to me that it builds fine also with setuptools 74.1.3
The `setuptools` requirement comes from
zopefoundation/meta#274
Many `zopefoundation` projects use `zc.buildout` to build
test environments. Apparently, (see PR mentioned above), new
`setuptools` versions tend to be incompatible with older `zc.buildout`
versions. The `zc.buildout` maintenance is not very active; therefore,
it can take significant time until a new version compatible with
newer `setuptools` becomes available.
I might be possible that `zope.interface` does not use itself
`zc.buildout` for its testing. However, many parts
(among them the `setuptools` requirement) are generated from a common
base used for all `zopefoundation` projects.
|
I am using setuptools version 75.6 and getting setuptools version mismatch. To solve this I removed the setuptools version.
|
|
See zopefoundation/meta#292 for reference. |
This limit on the setuptools requirement is only active when building the zope.interface package. It should be no problem to have a Python venv with setuptools 75 and still install zope.interface. But this depends on how you build or install it and especially whether that is in isolation or not. For example:
|
What is the reason to limit the version of setuptools to:
zope.interface/pyproject.toml
Line 6 in 7e0be48
It seems to me that it builds fine also with setuptools 74.1.3
The text was updated successfully, but these errors were encountered: