BLD: avoid deprecation warnings from setuptools when building on Python 3#155
Open
neutrinoceros wants to merge 1 commit intobrandon-rhodes:masterfrom
Open
BLD: avoid deprecation warnings from setuptools when building on Python 3#155neutrinoceros wants to merge 1 commit intobrandon-rhodes:masterfrom
neutrinoceros wants to merge 1 commit intobrandon-rhodes:masterfrom
Conversation
4bbf9fe to
725df25
Compare
This was referenced Mar 12, 2026
neutrinoceros
commented
Mar 12, 2026
Comment on lines
-79
to
-80
| 'Programming Language :: Python :: 3.8', | ||
| 'Programming Language :: Python :: 3.9', |
Author
There was a problem hiding this comment.
I'm removing these purely out of consistency with the existing CIBW_SELECT setting, but I note that I could probably easily re-introduce them later, virtually for free if #151 is accepted.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This addopts the standard license metadata format defined in https://peps.python.org/pep-0639/, which recent versions of setuptools have been pressing users to migrate to, since it clashes directly with their equivalent schema.
I tried to preserve Python 2 compat while keeping duplications to a minimum.