Add pyproject.toml and move metadata from setup.py #211
Conversation
JonathonReinhart
force-pushed
the
pyproject-toml
branch
from
e27eb11
to
9760eb1
Compare
This is a step toward modernizing the project packaging, and allows us to begin defining tooling config in pyproject.toml. References: - https://packaging.python.org/en/latest/specifications/declaring-project-metadata/ Tested: - python3 -m build - diff generated .dist-info/* files and ensure only minimal, expected changes
This the more modern, flexible frontend for building packages. Also, it provides build isolation which should avoid setuputils-version-related issues.
JonathonReinhart
force-pushed
the
pyproject-toml
branch
from
9760eb1
to
2c5ae0a
Compare
|
This build (and others) failed because the resulting dist is named The Maybe the right idea is to just invoke |
|
After switching to The reason is that Why not? Because when we run the tests from the project root, the How to fix this? My initial thought is to just blast
|
Also add names to all steps.
This will ensure that only the package from the installed wheel is used.
JonathonReinhart
force-pushed
the
pyproject-toml
branch
from
c766f2f
to
7c95e7f
Compare
This is a step toward modernizing the project packaging, and allows us to begin defining tooling config in
pyproject.toml.References:
Tested:
python3 -m buildscuba-*.dist-info/*files and ensure only minimal, expected changesCloses #203