-
Notifications
You must be signed in to change notification settings - Fork 5
Refactor repository to deploy as WHEEL via Github releases #178
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
|
I'm flying to Munich today and probably won't have a chance to look at this for at least a week, but it sounds good in principle and I have no objections if @FichteFoll wants to review it in the meantime. |
|
I'll take a look at it next weekend, probably. Edit: although I am in general in favor of ruff over black formatting. |
|
Have no strong favourite. Black just was an easy change. Feel free to change the formatter/checker. |
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.
|
I took a jab at it via #179, PTAL. |
Use single worker instance to perform both flake8 and pycodestyle checks. No need to spin up 2 separate VMs for those related tasks.
Stupid restriction, but despite a project supporting e.g. python 3.3, and only some secondary tools like sphinx needing more recent versions to run, uv fails to install it due to specified `required-python` value. Actually an argument to ditch uv, especially as all the CI is damn naive simple, and uv seems over the top for it, but well. It's the current hype.
ad1c037 to
d7d3926
Compare
|
Updated this PR, re-using most CI and workflow stuff from #179, but without changing any library code. I actually don't feel very comfortable with dynamically creating an additional I'd suggest to build a v1.6.0 release from this one and than upgrade library code from #179 to require python 3.8+ and release it as v1.7.0 or even v2.0.0 to denote the breaking change. |
deferred is the default in current releases
This commit enables python version specific releases without dedicated
releases or tag-prefixes by creating ...
sublime_lib-m.m.p-py33-none-any.whl
sublime_lib-m.m.p-py38-none-any.whl
which can be targetted by `"asset": "sublime_lib-*-${py_version}-none-any.whl"`
in repositories' release specification.
This PR...
Version is bumbed to 1.6.0, but this PR doesn't change any library functionality at all.