quality/blockerbugs
7
0
Fork 0
Code Issues 32 Pull requests 2 Projects 1 Releases Activity Actions
blockerbugs/requirements-development.txt

24 lines
377 B
Text
Raw Normal View History

requirements: remove unused imports, move some to devel reqs These requirements are no longer needed. Move pytest and munch to devel reqs, because they are only needed for tests. Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306 Co-authored-by: Kamil Páral <kparal@redhat.com>
2026-06-15 21:58:58 +02:00
## include production dependencies
Add ruff configuration and docs Co-authored-by: Kamil Paral <kparal@redhat.com> Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306
2026-06-01 16:13:23 +02:00
-r requirements.txt
requirements: remove unused imports, move some to devel reqs These requirements are no longer needed. Move pytest and munch to devel reqs, because they are only needed for tests. Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306 Co-authored-by: Kamil Páral <kparal@redhat.com>
2026-06-15 21:58:58 +02:00
## tests
Switch from Pagure to Forge for blocker review discussions This drops Pagure integration for creating and processing blocker discussion tickets and replaces it with a Fedora Forge (Forgejo) integration. Additional related changes are: - Testing is now performed through containers (Forgejo is one of those containers now) - docs/source/blockerbugs-workflow.md is added for a quick architecture overview for people and AI - docs/source/usage.md is added for a similar purpose documenting usage hints - docs/source/blockerbugscli.rst is extended for all commands - development setup instructions changed, using a different DB container with different variables - pytest configuration was moved from setup.cfg to pyproject.toml due to syntax escaping issues - a new pyforgejo dependency is added Related #296 Merges #299 Assisted-By: Claude Code
2026-01-23 15:16:39 +01:00
# tests use postgresql and forgejo containers
testcontainers ~= 4.14.0
requirements: remove unused imports, move some to devel reqs These requirements are no longer needed. Move pytest and munch to devel reqs, because they are only needed for tests. Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306 Co-authored-by: Kamil Páral <kparal@redhat.com>
2026-06-15 21:58:58 +02:00
pytest
pytest-cov
Add munch comment to requirements - add explanation comment why much is still required Fixes #318
2026-06-30 14:50:58 +02:00
# munch is required for bodhi-client type hinting
requirements: remove unused imports, move some to devel reqs These requirements are no longer needed. Move pytest and munch to devel reqs, because they are only needed for tests. Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306 Co-authored-by: Kamil Páral <kparal@redhat.com>
2026-06-15 21:58:58 +02:00
munch
Switch from Pagure to Forge for blocker review discussions This drops Pagure integration for creating and processing blocker discussion tickets and replaces it with a Fedora Forge (Forgejo) integration. Additional related changes are: - Testing is now performed through containers (Forgejo is one of those containers now) - docs/source/blockerbugs-workflow.md is added for a quick architecture overview for people and AI - docs/source/usage.md is added for a similar purpose documenting usage hints - docs/source/blockerbugscli.rst is extended for all commands - development setup instructions changed, using a different DB container with different variables - pytest configuration was moved from setup.cfg to pyproject.toml due to syntax escaping issues - a new pyforgejo dependency is added Related #296 Merges #299 Assisted-By: Claude Code
2026-01-23 15:16:39 +01:00
install code linters (flake8, mypy) Add new requirements-development.txt, which installs code linters. These linters often have editor/IDE integration, or can be run manually. Update development.rst to include some guidance. Create setup.cfg to have a centralized tool configuration. Move pytest.ini content into setup.cfg. (Also add a few more deprecation warning filters for our libraries).
2021-06-30 10:10:39 +02:00
## linters
Add ruff configuration and docs Co-authored-by: Kamil Paral <kparal@redhat.com> Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306
2026-06-01 16:13:23 +02:00
python-language-server[rope]
install code linters (flake8, mypy) Add new requirements-development.txt, which installs code linters. These linters often have editor/IDE integration, or can be run manually. Update development.rst to include some guidance. Create setup.cfg to have a centralized tool configuration. Move pytest.ini content into setup.cfg. (Also add a few more deprecation warning filters for our libraries).
2021-06-30 10:10:39 +02:00
mypy
Add ruff configuration and docs Co-authored-by: Kamil Paral <kparal@redhat.com> Related: https://forge.fedoraproject.org/quality/blockerbugs/issues/306
2026-06-01 16:13:23 +02:00
ruff
install code linters (flake8, mypy) Add new requirements-development.txt, which installs code linters. These linters often have editor/IDE integration, or can be run manually. Update development.rst to include some guidance. Create setup.cfg to have a centralized tool configuration. Move pytest.ini content into setup.cfg. (Also add a few more deprecation warning filters for our libraries).
2021-06-30 10:10:39 +02:00
## additional type hints for mypy
types-Flask
munch-stubs
types-requests
Set up CI and AI pull request review via Forgejo actions CI is a bit tricky because the requirement files are designed to match the rather odd environment we deploy blockerbugs in in production: Python 3.11 on RHEL 9 with almost all dependencies installed via pip. This includes compiling gssapi and krb5. So instead of my usual "just throw tox at it" approach, this replicates that same environment: we use an Alma 9 container, install the Python bits and the necessary compiler and devel dependencies, then use pip to install all the deps. Then we run the linters and the tests (not using `run` because this ancient pip on this ancient Python on this ancient RHEL doesn't install the binaries, you have to use `python -m`). The linters fail at present because there are lots of real problems; I assume nobody ran these checks for a while. I included a fix for the biggest flood of mypy issues, but otherwise I figured to leave the problems alone because I don't want to cause conflicts with the forgejo port PR. I figure once we get that PR merged we can then fix up the linting issues. But at least we'll have tests and AI review run on that PR while we work on it. Closes #300 Signed-off-by: Adam Williamson <awilliam@redhat.com>
2026-03-10 10:26:21 -07:00
types-setuptools
use python-versioneer for managing project version Instead of defining the app version statically, let python-versioneer discover it automatically for us from git. It uses a similar version format as `git describe`, i.e. the latest tag + number of additional commits + shorthash. Versioneer is installed statically, so that it also works if executed outside of git (in that case, depending on how it was created, it might only display a git hash without additional attributes). During development and with proper tagged releases, or when installed directly from the git repo (as in OpenShift), it should display the version correctly and also the commit date as a bonus, in the web footer. When building docs, it is now recommended to install sphinx into virtualenv (or not use venv at all), otherwise the version can't be determined. One unresolved issue is that specfile versioning is not integrated, i.e. it still needs to be updated manually. The Makefile support is also poor. I suppose we'll want to get rid of the spec file and possibly large portion of the Makefile soon anyway, and that's why I haven't invested time to fix it at this moment. Since we don't use it now, it shouldn't be much of a problem. Fixes: https://pagure.io/fedora-qa/blockerbugs/issue/236 Merges: https://pagure.io/fedora-qa/blockerbugs/pull-request/239
2022-02-22 15:11:39 +01:00
## documentation
sphinx
Reference in a new issue Copy permalink