chore: modernize Python tooling (uv, pyproject.toml, src layout, semantic release)#283
chore: modernize Python tooling (uv, pyproject.toml, src layout, semantic release)#283salman2013 wants to merge 5 commits into
Conversation
Replaces setup.py with pyproject.toml using PEP 621 static metadata, setuptools-scm for dynamic versioning, and importlib.metadata for __version__. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Replaces requirements/*.txt/in files with uv dependency groups in pyproject.toml (test-base, test, django42, quality, ci, dev), adds tox.ini with uv-venv-lock-runner and a Django version matrix, and updates CI to use astral-sh/setup-uv with uv sync/run tox. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds [tool.semantic_release] config using setuptools-scm for dynamic versioning, and replaces the tag-triggered pypi-publish.yml with a release.yml that runs CI, cuts a release, and publishes to PyPI via OIDC trusted publisher. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Moves crowdsourcehinter/ to src/crowdsourcehinter/ and updates pyproject.toml (where = ["src"]), tox.ini, and pytest.ini paths accordingly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
openedx-webhooks
added
open-source-contribution
|
Thanks for the pull request, @salman2013! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
- Add [flake8] max-line-length = 127 to tox.ini to match original CI config - Add noqa: F401 to intentional CrowdsourceHinter re-export in __init__.py - Fix pre-existing style violations in crowdsourcehinter.py (E203, E231, E261, E303, E501, W291, W293) - Remove django test envs from CI matrix until tests are written Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
@feanil can you help with reviewing this? |
3 participants
Summary
setup.pytopyproject.toml(PEP 621) withsetuptools-scmfor dynamic versioning andimportlib.metadatafor__version__pip-tools+requirements/withuvdependency groups (test-base,test,django42,quality,ci,dev), addstox.iniwithuv-venv-lock-runnerand a Django 4.2/5.2 version matrix, and updates CI to useastral-sh/setup-uv[tool.semantic_release]config andrelease.ymlworkflow (runs CI → cuts release → publishes to PyPI via OIDC), replaces the old tag-triggeredpypi-publish.ymlsrc/crowdsourcehinter/layoutTest plan
make qualitypasses (tox -e quality)make testpasses (tox -e py312-django42andtox -e py312-django52)quality,py312-django42,py312-django52release.yml)🤖 Generated with Claude Code