Skip to content
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

Require setuptools 68.2 or higher for building the package. #385

Merged
merged 3 commits into from
Sep 16, 2023

Conversation

mauritsvanrees
Copy link
Member

When built with setuptools 68.1, you could not import the package, at least not an editable package. Note that you can still install this package with older setuptools versions. See Plone meta issue 172 for details.

New problem though. tox -e dependencies says:

ERROR Missing dependencies:
	setuptools>=68.2

I tried with `setuptools<68.1', which would also work, but that only changes the message:

ERROR Missing dependencies:
	setuptools<68.1

I think this is a shortcoming in z3c.dependencychecker. It should not report this as a missing dependency. It should see that pyproject.toml has this dependency covered.

We definitely should not require setuptools>=68.2 in install_requires.

When built with setuptools 68.1, you could not import the package, at least not an editable package.
Note that you can still *install* this package with older setuptools versions.
See [Plone meta issue 172](plone/meta#172) for details.

New problem though.  `tox -e dependencies` says:

```
ERROR Missing dependencies:
	setuptools>=68.2
```

I tried with `setuptools<68.1', which would also work, but that only changes the message:

```
ERROR Missing dependencies:
	setuptools<68.1
```

I think this is a shortcoming in `z3c.dependencychecker`.  It should not report this as a missing dependency.
It should see that `pyproject.toml` has this dependency covered.

We definitely should *not* require `setuptools>=68.2` in `install_requires`.
@mister-roboto
Copy link

@mauritsvanrees thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@mauritsvanrees mauritsvanrees marked this pull request as ready for review September 7, 2023 13:56
@mauritsvanrees
Copy link
Member Author

@gforcada Do you remember the reason for adding --no-isolation to the build commands? It seems faster. If that was the only reason, then my changes here should be fine. They should be done in all or most other packages as well.

@mauritsvanrees
Copy link
Member Author

Let's check on Jenkins for good measure.
@jenkins-plone-org please run jobs

@gforcada
Copy link
Member

Sorry for the lateness, indeed the --no-isolation was mostly for speed reasons 👍🏾

@mauritsvanrees mauritsvanrees merged commit e040c0e into master Sep 16, 2023
6 checks passed
@mauritsvanrees mauritsvanrees deleted the maurits-minimum-setuptools-version-for-build branch September 16, 2023 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants