interrogate icon indicating copy to clipboard operation
interrogate copied to clipboard

Move build system to UV, add vscode debugger/test ui, add python 3.13 build/test target

Open nateinaction opened this issue 7 months ago • 1 comments

Hey Lynn,

I playfully (🪂) worked my way toward debugging issue #187. To start that journey I wanted to update some of the developer tooling to help me get to debugging a little quicker. I also needed to update the CI system to get builds passing since some of the action images had been deprecated and removed. What do you think?

  • Moved to using UV for python environment management

  • Updated contributing readme with new uv based commands

  • A teensy weensy code change in badge_gen.py to satisfy mypy

  • Another teensy weensy code change in badge_gen.py to prevent an OSError from ruining the day

    E   OSError: no library called "cairo-2" was found
    E   no library called "cairo" was found
    E   no library called "libcairo-2" was found
    
  • Added testing for python 3.13 and set that as the latest version

  • Updated all ci dependencies because ci was broken Captura de pantalla 2025-06-30 a la(s) 19 05 44

  • Added support for running tests in vscode ui Captura de pantalla 2025-06-30 a la(s) 18 46 56

  • Added support for running the debugger in vscode Captura de pantalla 2025-06-30 a la(s) 18 48 19 Captura de pantalla 2025-06-30 a la(s) 19 32 58

  • Improved error message when interrogate encounters a syntax error in a codebase

Before Captura de pantalla 2025-06-30 a la(s) 20 50 41

After Captura de pantalla 2025-06-30 a la(s) 20 50 51

Have you tested this? If so, how?

All tests running in CI and I have tested all contributor doc commands locally.

Checklist for PR author(s)

  • [x] Changes are covered by unit tests (no major decrease in code coverage %).
  • [x] All tests pass.
  • [x] Docstring coverage is 100% via tox -e docs or interrogate -c pyproject.toml (I mean, we should set a good example :smile:).
  • [x] Updates to documentation:
    • [x] Document any relevant additions/changes in README.rst.
    • [x] Manually update both the README.rst and docs/index.rst for any new/changed CLI flags.
    • [ ] Any changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives. Find the appropriate next version in the project's __init__.py file.

Release note

- Improved error message when encountering syntax errors in a codebase

Solves #187

nateinaction avatar Jul 01 '25 00:07 nateinaction

Happy Monday @econchick! I've updated the PR to use the uv build backend which is now stable.

nateinaction avatar Jul 07 '25 22:07 nateinaction