Conversation
ofek
force-pushed
the
modernize-metadata
branch
2 times, most recently
from
4ed3dd8 to
b581969
Compare
Contributor
Author
|
CI just looks flaky https://pypi.org/project/tomli/#history |
ofek
force-pushed
the
modernize-metadata
branch
from
b581969 to
e7733b3
Compare
ofek
force-pushed
the
modernize-metadata
branch
3 times, most recently
from
d349583 to
39f2185
Compare
ofek
force-pushed
the
modernize-metadata
branch
from
39f2185 to
63c69d2
Compare
Contributor
Author
|
AZP has old PyPy 3.6 |
jirikuncar
approved these changes
Feb 25, 2022
Member
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
skarimo
approved these changes
Feb 25, 2022
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
3 participants
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.
What does this PR do?
This implements PEP 621, obviating the need for both
setup.pyandMANIFEST.in. Support has not landed insetuptools, so builds will now usehatchling. We also did this for all integrations: https://github.com/DataDog/integrations-coreThis also drops support for EOL Python 3.x versions since
hatchlingand other build backends likesetuptoolshave already done so. This will not break anything becausepiponly looks for version candidates that satisfy therequires-pythonfield. Here are stats for the curious: https://pypistats.org/packages/datadogNote that the
setup.pyfile will be removed when we drop Python 2 since new-style editable installations require versions ofpipthat are Python 3-only. Basically, this is just for thepy27testtoxenvironment.