Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
zacharyburnett
force-pushed
the
pep621
branch
from
60d97e7 to
33c5eb5
Compare
jmr
left a comment
jmr
left a comment
There was a problem hiding this comment.
Could you give a bit more info than just "apply PEP 621"? I don't know anything about Python packaging, so a few sentences of explanation would be helpful.
https://google.github.io/eng-practices/review/developer/cl-descriptions.html#informative
|
@selimnairb This is moving the |
@jmr Yes, I'll pull it down today and have a look. |
Co-authored-by: Zach Burnett <[email protected]>
|
Thanks! |
3 participants
PEP621 (https://peps.python.org/pep-0621/) defines using the
pyproject.tomlfile to store project metadata in the[project]table. This has several advantages over usingsetup.cfgorsetup.pyto store the project metadata, namely:pyproject.tomlis required by PEP517 (https://peps.python.org/pep-0517/) and many third party tools use it to store their configurationsetuptools(such ashatchormeson) to read the same project metadata