-
Notifications
You must be signed in to change notification settings - Fork 4
Structural updates, require Python 3.8, deploy a WHEEL file #179
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
base: master
Are you sure you want to change the base?
Conversation
By uploading a Python Wheel, we will not be restricted in our folder structure anymore.
Since this folder won't be used as a dependency directly anymore.
The next version will definitely require Python 3.8, so we can drop all the compatibility-related stuff.
It only contains dev dependencies currently but will be useful for reproducible CI environments.
IMHO, we should first create a py33 compatible WHEEL release, targeting legacy ST3/4 builds, to totally get rid of legacy dependency releases without breaking unmaintained py33 packages on ST3/4 platform. A 2nd step then would be to upgrade code base to a py38-only version. |
| requires-python = ">=3.8,<=3.9" | ||
|
|
||
| [build-system] | ||
| requires = ["hatchling>=1.20", "hatch-vcs>=0.4"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's wrong with flit?
|
For python 3.8 it may be useful to disable annotation evaluation via |
This is an alternative approach to #178, using it as an inspiration but going about it slightly differently.
I tried to isolate commits into reasonable chunks.
Things I did:
st3tosrc).uvfor our toolchain.Things I did not do:
uv build.