Repository navigation
Conversation
Bomme
force-pushed
the
pip_package
branch
2 times, most recently
from
October 22, 2026 18:36
dc1c652 to
96c976b
Compare
- Updated pyproject.toml with project metadata, dependencies, and build system configuration. - Removed setup.py as it is no longer needed with the new configuration. - Modified GitHub Actions workflow to support multiple Python versions and updated installation steps.
…workflow for publishing to PyPI
python 3.7 is no longer supported in ubuntu-latest
- Require Python >=3.9 and update classifiers (3.9-3.14) - Use SPDX license expression (MIT) with license-files; require hatchling >=1.27 - Add Issues/Documentation URLs and a dev dependency group - publish workflow: bump retired upload/download-artifact@v3 to v5 and drop redundant setup-python step - smoke test workflow: test 3.9-3.14 on ubuntu-latest using setup-uv
Run examples.py live on every supported Python (3.9-3.14), one version at a time with a 30s pause before each run, to stay under Freesound's throttling (60 requests/minute). Also check that the package imports and builds in each job.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Packaging and CI setup for the project, transitioning from
setup.pyto a PEP 621-compliantpyproject.toml, usinguvas front-end andhatchlingas build backend.Packaging and Publishing Improvements:
pyproject.tomlfile with project metadata, dependencies, build system configuration, and support for Python 3.9–3.14, enabling modern packaging standards and future PyPI publishing.freesoundsetup.pyfile, fully switching to the new build system..github/workflows/publish.yml) for automated building and publishing of releases to PyPI.Continuous Integration Updates:
uvfor dependency management and running tests, and improved reliability withfail-fast..python-versionfile specifying Python 3.13 for local development environment consistency.Before releasing
freesoundproject (or a pending trusted publisher) on PyPI and apypienvironment on GitHub.pyproject.tomlstill says 1.1)