Migrate from poetry to uv #135
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



What's included in this PR
Migration from
poetrytouv(https://docs.astral.sh/uv/).poetrywithuvas package and build manager.pip-auditto scan dependencies for known vulnerabilities. See https://github.com/pypa/pip-audit.Tasks
Tasks related to migration to uv:
pyproject.tomland dependencies.uv build)uv. See https://docs.astral.sh/uv/guides/integration/github/.Other tasks:
codeql. Currently set up incodeql.yml(may not need any update).flake8(error and style linter, complexity analysis). Currently included intest.yml, but may possibly be replaced with the github action.bandit(security linter). Scan for common security issues in python code.pip-audit. Scans dependencies for known vulnerabilities.Note
This branch is established from the add-python313-support branch (see PR #133), and therefore includes multiple commits related to an attempt to add support for python versions 3.8 through 3.13 using poetry.
If this PR is merged to master branch, then PR #133 should be closed without merging.