Skip to content
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

support pep621 #373

Closed
graingert opened this issue Aug 21, 2021 · 4 comments
Closed

support pep621 #373

graingert opened this issue Aug 21, 2021 · 4 comments

Comments

@graingert
Copy link
Contributor

graingert commented Aug 21, 2021

pep621 is now publicly supported and documented in flit, zest.releaser should support it also by setting the pyproject.toml :

[project]
version = "0.0.0a0"

field

(While preserving quote type too)

@graingert
Copy link
Contributor Author

Also if zest sees this field it should take priority over any version in any other location, eg setup.py/cfg

@regebro
Copy link

regebro commented Mar 27, 2022

I looked into this a bit more, and I think supporting this doesn't really make any sense unless zest.releaser also supports building the package with flit, so in essence I think this really is fully a part of #295.

@graingert
Copy link
Contributor Author

Setuptools 61 now supports PEP 621 (and setup.cfg is pending deprecation)

@mauritsvanrees
Copy link
Member

Version 8.0.0a1 supports writing the version to pyproject.toml.
For releasing you still need a setup.py for now. currently zest.releaser simply checks if there is a setup.py. If it is not there, zest.releaser does not create distributions, and does not push to PyPI. That will hopefully be for later in the alpha stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants