Skip to content

Drop setuptools-scm requirement in wheels #21820

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

Merged
merged 1 commit into from
Dec 1, 2021

Conversation

QuLogic
Copy link
Member

@QuLogic QuLogic commented Nov 30, 2021

PR Summary

Fixes #21783.

PR Checklist

Tests and Styling

  • [n/a] Has pytest style unit tests (and pytest passes).
  • Is Flake 8 compliant (install flake8-docstrings and run flake8 --docstring-convention=all).

Documentation

  • [n/a] New features are documented, with examples if plot related.
  • [n/a] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
  • [n/a] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).
  • [n/a] Documentation is sphinx and numpydoc compliant (the docs should build without error).

@QuLogic QuLogic added the Build label Nov 30, 2021
@QuLogic QuLogic added this to the v3.5.1 milestone Nov 30, 2021
# Installing from a git checkout.
["setuptools_scm>=4"] if Path(__file__).with_name(".git").exists()
else []
# Installing from a git checkout that is not producing a wheel.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why exactly is having this in setup_requires insufficient? Or is that only going to work with pyproject.toml?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know; this came in with the original PR #18971; would have to ask @anntzer for the exact reason.

Copy link
Contributor

@anntzer anntzer Dec 1, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #18971 (comment) and #18971 (comment): the two options were either
(a) don't have a runtime dep on setuptools_scm, and accept that inplace installs get the wrong version if one does pip install -e . and then update the git repo (the version comes from _version.py and is only updated when setup.py is run, either directly (e.g. when recompiling) or via pip); or
(b) make setuptools_scm a dependency so that the version is always correct.

I was actually in favor of (a) (as described in that thread), but didn't feel that strongly about it. I guess that's another opportunity to go back to (a) :-)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

accept that inplace installs get the wrong version if one does pip install -e .

Do you mean that the wrong version gets reported, or that the install doesn't work? I think reporting the current commit in the version is nice, but hardly crucial.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wrong version gets reported if one does pip install -e and then updates the git repo (and even then, there are probably workarounds possible e.g. using git hooks...).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As noted in #21783, my solution has been to import and use setuptools_scm, then fallback to importlib_metadata. Given the fallback, it seemed fine to treat setuptools_scm as an optional dependency and only list it as a "build" dependency. It's not perfect, but I've gone to statically listing all package metadata in setup.cfg.

@tacaswell tacaswell mentioned this pull request Dec 1, 2021
@tacaswell
Copy link
Member

I agree with @QuLogic that this is the minimal fix for the wheels and adopting something more like @dopplershift 's metpy example for 3.6

@QuLogic
Copy link
Member Author

QuLogic commented Dec 1, 2021

Here is a test build for wheels with this patch:
https://github.com/QuLogic/matplotlib/actions/runs/1523259905
I believe there is no longer a setuptools-scm requirement.

@tacaswell
Copy link
Member

I also checked by hand locally with the right env set and did not have the dependency.

Copy link
Contributor

@dopplershift dopplershift left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine enough for a bugfix release.

@tacaswell tacaswell merged commit 59732ac into matplotlib:main Dec 1, 2021
meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull request Dec 1, 2021
@QuLogic QuLogic deleted the no-wheel-setuptools-scm branch December 1, 2021 22:23
QuLogic added a commit that referenced this pull request Dec 2, 2021
…820-on-v3.5.x

Backport PR #21820 on branch v3.5.x (Drop setuptools-scm requirement in wheels)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[MNT]: wheel of 3.5.0 apears to depend on setuptools-scm which apears to be unintentional
6 participants