We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We should probably upgrade from setup.py to pyproject.toml.
I've been using uv to manage all my Python projects recently and I like it much more than poetry.
I will put together a PR to migrate to using uv, including refactoring some folders and CI scripts.
The text was updated successfully, but these errors were encountered:
Same, just note that uv resolves differently than pip, which might sometimes be a problem (see discussion in e.g. MIT-LCP/wfdb-python#511).
In any case, migrating to pyproject.toml is the default nowadays, which we should do no matter what.
pyproject.toml
Sorry, something went wrong.
uv
Successfully merging a pull request may close this issue.
We should probably upgrade from setup.py to pyproject.toml.
I've been using uv to manage all my Python projects recently and I like it much more than poetry.
I will put together a PR to migrate to using uv, including refactoring some folders and CI scripts.
The text was updated successfully, but these errors were encountered: