Migrate to modern Python tooling (uv, pyproject.toml, semantic-release)

[salman2013]

Summary

• Phase 1 — Consolidate all package metadata into `pyproject.toml` (PEP 621): static dependencies, SPDX license, setuptools-scm for dynamic versioning, coverage config, isort config; delete `setup.py`, `setup.cfg`, `.coveragerc`
• Phase 2 — Replace pip-tools with uv: `[dependency-groups]` (PEP 735), `uv.lock`, updated `tox.ini` to use `tox-uv` + `uv-venv-lock-runner`, updated `Makefile` and CI workflow to use `uv sync`/`uv run tox`
• Phase 3 — Add `python-semantic-release` for automated versioning and PyPI publishing via OIDC trusted publisher; delete legacy `pypi-publish.yml`
• Phase 4 — Migrate to `src/` layout: move `openassessment/` → `src/openassessment/`, add `where = ["src"]` to `pyproject.toml`, update Makefile, scripts, MANIFEST.in, and karma.conf.js paths

Test plan

• CI passes on this PR (`django42`, `django52`, `js`, `quality` environments)
• Configure OIDC trusted publisher on PyPI for `openedx/edx-ora2` → workflow `release.yml` before merging

🤖 Generated with Claude Code

[openedx-webhooks]

Thanks for the pull request, @salman2013!

This repository is currently maintained by @openedx/openedx-unmaintained.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To 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:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where 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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.53%. Comparing base (b60672e) to head (51a0014).
⚠️ Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2423      +/-   ##
==========================================
+ Coverage   95.46%   95.53%   +0.06%     
==========================================
  Files         198      198              
  Lines       22842    22820      -22     
  Branches     1551     1549       -2     
==========================================
- Hits        21807    21801       -6     
+ Misses        780      765      -15     
+ Partials      255      254       -1     

Flag	Coverage Δ
unittests	95.53% <100.00%> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[itsjeyd]

Hi @salman2013, thank you for your contribution! Please let us know when it is ready for review.

[irfanuddinahmad]

Same as acid-block#282: {name = "edX", email = "oscm@edx.org"} is the legacy convention. This migration effort has standardized on {name = "Open edX Project", email = "oscm@openedx.org"}, matching sample-plugin's actual current pyproject.toml.

[irfanuddinahmad]

This one doesn't look addressed yet — pyproject.toml still has {name = "edX", email = "oscm@edx.org"}. Please update to {name = "Open edX Project", email = "oscm@openedx.org"} per the migration convention.

[salman2013]

@irfanuddinahmad Fixed c621fc3

[irfanuddinahmad]

Confirmed — pyproject.toml now has {name = "Open edX Project", email = "oscm@openedx.org"}. Thanks for the fix. Resolving.

[itsjeyd]

Hi @salman2013, it looks like one of the coverage checks is failing here. Could you have a look?

[salman2013]

@itsjeyd All tests are green now.

[itsjeyd]

Thanks @salman2013.

@openedx/axim-engineering Pinging you here since this repo is currently unmaintained.

This PR got approval from a CC earlier (#2423 (review)) and has a green build. Could you please have a look and merge the changes if they look good to you as well?

[feanil]

python -m build --wheel fails on this branch:

error: can't copy 'src/openassessment/locale': doesn't exist or not a regular file

src/openassessment/locale is a git-tracked symlink to conf/locale, and setuptools-scm's file finder puts every git-tracked path into SOURCES.txt, so build_py tries to copy the symlink as a file. origin/master builds fine. PSR runs build_command before it commits or tags, so the first push to master after this merges fails there and no version publishes.

The comment here is wrong too. MANIFEST.in's recursive-include src/openassessment/locale *.mo does copy through the symlink: published 7.1.1 and a build off this branch both carry the same 77 .mo files under openassessment/locale/, so conf/locale/** only adds a second copy of them.

[feanil]

Once the build is fixed the wheel is 957 files / 4,878,011 bytes, against 466 / 2,601,590 for PyPI 7.1.1. Nothing that shipped before is dropped. What is new is 154 duplicate locale files under openassessment/conf/locale/, 191 test and spec files including 101 fixtures under openassessment/xblock/test/data, and the sass sources, xblock/static/xml and the font-awesome fonts.

include-package-data defaults to true under pyproject.toml, and with setuptools-scm's file finder that means every git-tracked file under a package directory, so neither MANIFEST.in nor [tool.setuptools.package-data] bounds the wheel any more. Widening this exclude to cover *.test is not enough on its own; I tried it and the files still ship as package data of the parent package.

Get the wheel back to what 7.1.1 shipped.

[feanil]

docs is in the tox envlist but not in this matrix, and it is red: tox -e docs stops at doc8 docs/ with 105 errors across 8 files. That env is the only place that runs python -m build --wheel and twine check, which is what would have caught the wheel not building.

Add docs to the matrix and fix the doc8 failures.

[feanil]

.github/release_process.md still says to bump the version in openassessment/__init__.py and package.json and then hand-create a matching release tag. That path no longer exists, the Python version comes from git tags now, and semantic-release creates the tag. Update it here.