teilchensammler/requirements/dev.in

-r test.in

django-debug-toolbar  # debugging in the browser
django-stubs          # type hints for django
ipython               # more colorful repl
pip-compile-multi     # superior dependency management
rich                  # pretty exceptions on dev/console
ruff                  # linter
uv                    # resolver for pip-compile-multi
genbadge[tests,coverage]  # create badges from coverage reports and pytest
pymarkdownlnt         # lint markdown files, note: it's "lnt" at the end, not "lint"
pytest-randomly       # run tests in random order; installed in dev env because in test/ci we want more reproducibility
[dependencies] split them up further 2025-03-13 19:25:18 +01:00			`-r test.in`
[dependencies] add requirements files, managed by pip-compile-multi 2025-03-12 17:29:12 +01:00
[dependencies] add comments explaining why we added those dev dependencies 2025-03-17 18:27:38 +01:00			`django-debug-toolbar # debugging in the browser`
			`django-stubs # type hints for django`
			`ipython # more colorful repl`
			`pip-compile-multi # superior dependency management`
			`rich # pretty exceptions on dev/console`
			`ruff # linter`
			`uv # resolver for pip-compile-multi`
[flair] generate badges from pytest and coverage reports dev only, doesn't yet need to run on CI 2025-03-18 00:18:31 +01:00			`genbadge[tests,coverage] # create badges from coverage reports and pytest`
[dependencies] add pymarkdownlnt to lint markdown files mind the package name: it is pymarkdonlnt (l-n-t) 2025-03-18 11:45:42 +01:00			`pymarkdownlnt # lint markdown files, note: it's "lnt" at the end, not "lint"`
[deps] add pytest-randomly to run tests in random order ATM it is intended for use in dev env, not test env. On test/ci we want a more reproducable order (...I think). 2025-06-21 03:10:15 +02:00			`pytest-randomly # run tests in random order; installed in dev env because in test/ci we want more reproducibility`