using uv for dev setup, build, publish #114
Open
+177
−140
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.
This pull request includes several significant changes to the build and testing workflows, dependency management, and documentation. The most important changes are detailed below:
Workflow and Build Process Updates:
test.yml
toci.yml
to handle testing, building, and releasing the project. This includes steps for setting up Python environments, running tests with Tox, building the package, and publishing releases to PyPI and GitHub.Dependency Management:
.devcontainer/on_create_command.sh
to use theuv
tool for installing dependencies and tools such asruff
andtox
.pyproject.toml
to include a new[dependency-groups]
section for development dependencies and updated the build system requirements.Documentation Updates:
checklist.rst
to reflect the new release procedure, including creating GitHub releases and updating the PyPI page.doc/dev.rst
to useuv
for setting up the development environment.Configuration and Metadata:
setup.cfg
as part of the transition to usingpyproject.toml
for configuration.sphinx_intl/__init__.py
to dynamically fetch the package version usingimportlib.metadata
.These changes streamline the development and release processes, improve dependency management, and update the project documentation to reflect the new workflows.