Conversation
|
Oh... |
|
Discussion on dropping 3.6 support #2136 |
|
What do we think about this bit at the top of the setuptools docs page…?
Presumably the idea if we go with this, we'd switch all Encode projects over as well eventually. Is now a good time? Also, what does this get us compared to the current |
Maybe not. Let's wait for others to test this first 😅 👍
One less file (setup.py), and compliance with the mentioned PEP. |
|
For another point of comparison, I played with |
Co-authored-by: Florimond Manca <florimond.manca@protonmail.com>
Co-authored-by: Florimond Manca <florimond.manca@protonmail.com>
Co-authored-by: Florimond Manca <florimond.manca@protonmail.com>
|
Thanks for the review @florimondmanca 🙇 I've updated the PR, sync with the changes that happened on |
|
It adds correctly the I've added the |
|
Let's wait for @tomchristie 's opinion here? |
| @@ -0,0 +1,61 @@ | |||
| [build-system] | |||
| requires = ["setuptools", "setuptools-scm"] | |||
There was a problem hiding this comment.
I think we should add a minimal version of setuptools as a build requirement to ensure that a compatible version of setuptools is installed.
| requires = ["setuptools", "setuptools-scm"] | |
| requires = ["setuptools>=61", "setuptools-scm"] |
|
This was brought on Kludex/starlette#1359.
setuptools released 0.61.0 yesterday, and brought to light the PEP-621 which makes this PR possible. Most of the PR was inspired on this page: https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html
Notes:
I'll continue later on. I need to check if everything is included on the metadata files.How to test?
./scripts/buildto see that wheel andtar.gzare generatedpython -m pip install -e .for editable installs