build: Modernize xapi-db-load: migrate to uv, pyproject.toml, PEP 735 dependency groups

[farhan]

Important

PR implemented with the assistance of Claude Code. Refined and validated before being submitted for code review.

Modernize `xapi-db-load`
Part of openedx/public-engineering#506

Summary

• Replace `setup.py`/`setup.cfg` with `pyproject.toml` (PEP 621 static metadata)
• Switch from pip-compile to `uv` with PEP 735 dependency groups; commit `uv.lock`
• Retain pylint/isort/pycodestyle/pydocstyle/mypy as on master.
• Coverage config moved into `pyproject.toml`
• Update CI to use `astral-sh/setup-uv`; SHA-pin all actions
• Fix `MANIFEST.in`: corrected `recursive-include xapi-db-load` (hyphen — never matched the package dir) to `xapi_db_load` (underscore); source distributions were previously missing all package data files
• Add `quality` and `docs` envs to CI matrix (were not run on master)
• Fix `tox -e docs` failures: mock `chdb` import, force-regenerate stale RST files, remove unsupported `logo_only` theme option
• Fix `tox -e quality` failures: fix pre-existing pylint violations at source; suppress mypy errors for pre-existing code; add `build` to quality deps; enforce isort multi-line import style
• Regenerate `pylintrc` with edx-lint 6.1.0 (was already pinned at 6.1.0 but `pylintrc` had been generated with 5.3.0)

Removed/Updated

Deleted files: `setup.py`, `setup.cfg`, `requirements/`, `.coveragerc`, `codecov.yml`

Updated Makefile targets:

Target	Change
`upgrade`	Replaced pip-compile workflow with `uv run edx_lint write_uv_constraints` + `uv lock --upgrade`
`requirements`	Replaced pip-sync with `uv sync --group dev` + `uv tool install tox --with tox-uv`
`quality`	Removed `*.py` glob from linter commands (`setup.py` was the only root-level `.py` file; glob would expand to nothing after deletion); replaced `python setup.py bdist_wheel` with `uv run python -m build`

Versioning

`version = "3.1.0"` declared directly in `pyproject.toml` — master had no PyPI publish workflow, so `setuptools-scm` is not used and the version is bumped manually on each release tag.

Quality / Docs CI

These envs were added to the CI matrix in this PR. All failures fixed are pre-existing (master never ran these checks in CI):

• pylint: fixed violations at source where possible (sys.exit, super(), enumerate, generators, implicit booleanness, renamed built-in shadowing). For violations that require structural refactoring (abstract method hierarchies, intentional signature narrowing in xapi subclasses, pytest fixture patterns, circular import avoidance), added inline `# pylint: disable` comments at the specific location with a justification comment. No global suppression in `pylintrc_tweaks`.
• mypy: added `ignore_errors = true` override for all `xapi_db_load.*` modules — master never ran mypy in CI and there are ~94 pre-existing type errors across the codebase. This allows mypy to remain configured and runnable without failing on pre-existing issues.
• pycodestyle: added `W503` (line break before binary operator — deprecated by pycodestyle, conflicts with W504) and `W505` (doc line too long — already enforced by pylint's `max-doc-length`) to ignore list
• isort: added `force_grid_wrap = 2` to preserve the existing multi-line-per-name import style; isort was previously collapsing multi-line imports onto one line when they fit within the 120-char limit, which conflicts with the style used throughout the codebase
• docs: mocked `chdb` (broken on macOS but works in Linux CI), force-regenerated stale RST files with `sphinx-apidoc -f`

Important Notes

• This repo does not publish to PyPI, so `src/` layout was not adopted.
• This repo has no PyPI publish workflow on master, so `python-semantic-release` and `release.yml` were not added.
• `codecov.yml` was deleted because it contained a hardcoded 74 % patch-coverage target that is not enforced by any current CI gate; Codecov config can be re-added with deliberate thresholds if desired.
• `tox -e py312` fails locally on macOS because `chdb` crashes at import time on this platform (broken native extension). The same failure exists on master. CI runs on Linux where `chdb` works correctly.

Testing Notes

This PR has not been manually tested against the repo's own features. Testing relied on CI checks and local agent tooling (`make requirements`, `make lint`, `make test`, `python -m build`). Repo-owner is encouraged to run the repo's feature tests before merging.

---

🤖 Generated with Claude Code

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

[irfanuddinahmad]

Solid migration overall — dependency list matches 1:1 with the old requirements/base.in, version handling is consistent, and I also want to flag a nice incidental fix: MANIFEST.in's recursive-include xapi-db-load ... (hyphen — never matched the real xapi_db_load package dir) is corrected to the underscore form. Worth a line in the PR description since it's a real behavior change, not just tooling.

One gap worth closing before merge:

tox.ini's envlist gains docs and quality (envlist = py312, docs, quality), and both env definitions are correctly wired to dependency_groups. But .github/workflows/ci.yml's matrix still only runs toxenv: [py]. So make quality (pylint/pycodestyle/pydocstyle/mypy/isort) and the docs build still never run in CI — same gap as before this PR, but now that the scaffolding exists, it'd be low-cost to close it. forum#283 (same author, same day) does add quality/docs to its CI matrix — worth matching that here for consistency.

[farhan]

Thanks for the thorough review, @irfanuddinahmad!

Both points addressed in the latest commit:

• CI matrix — added quality and docs to .github/workflows/ci.yml's toxenv list, matching the pattern from forum#283.
• MANIFEST.in fix — added a bullet in the PR description calling it out as a real behavior change (source distributions were silently missing all package data files before).

[farhan]

@irfanuddinahmad PR is available for the next pass

[irfanuddinahmad]

CI is green (7/7). The MANIFEST.in hyphen/underscore fix is a nice incidental catch (source dists were silently missing package data before). The previously flagged gap — quality/docs tox envs not wired into the CI matrix — is fixed; verified the matrix now includes toxenv: [py, quality, docs] at the PR head commit. LGTM.

[feanil]

Why do we need test requirements for the docs build?

[irfanuddinahmad]

Confirmed reason: docs/xapi_db_load.tests.rst (part of this PR's docs, unchanged content) has .. automodule:: xapi_db_load.tests.test_backends and five sibling automodule directives for the other test modules -- Sphinx's autodoc extension actually imports each of those modules to pull docstrings/members, so whatever those test files import at module scope has to be installed for the docs build to succeed, not just for running pytest. That's why doc includes {include-group = "test"} here.

[farhan]

This mirrors master — doc.in has -r test.txt, so I added {include-group = "test"} here

[feanil]

Looks like you're missing setuptools-scm and semantic release here as well.

[irfanuddinahmad]

Checked -- this is intentional, not a gap. xapi-db-load isn't published to PyPI at all (confirmed: pypi.org/pypi/xapi-db-load/json 404s), and it's not meant to be -- it's a CLI tool distributed via [project.scripts] (line 39-40: xapi-db-load = "xapi_db_load.main:cli"), installed directly from the repo. setuptools-scm + python-semantic-release exist to version and publish packages people pip install; there's no release artifact here for them to version. This matches the pattern used for the other application-style (non-published) repos in this same migration effort -- they skip Phase 3 (semantic-release) entirely and keep a plain static version in pyproject.toml like this one does.

[farhan]

xapi-db-load is in the hardcoded non-PyPI list for this migration cycle — it has no PyPI publish workflow on main. Non-PyPI repos use a static version = "x.y.z" in pyproject.toml; setuptools-scm and python-semantic-release are intentionally omitted.

[farhan]

@feanil PR is available for the next pass, feel free to squash-merge if all seems alright now.

[feanil]

@farhan it looks like maybe there were updates to the requirements files that we need to resolve, probably a make upgrade merged while waiting for this. I've enabled auto merging so it should merge if all the tests pass and the conflicts are resolved.