oncall-engine/engine/requirements-dev.txt
Matias Bordese c1b279aab8
Use pip-tools to handle Python deps (#3892)
[pip-tools](https://github.com/jazzband/pip-tools) helps making builds
deterministic, controlling deps (and indirect deps) upgrades (and
versions consistency) avoiding unexpected (and potentially breaking)
changes.

We keep our direct deps in `requirements.in` from which we generate the
`requirements.txt` (where *all* deps are pinned). We also constrain dev
(and enterprise) deps based on base requirements.

Check how to [update
deps](https://github.com/jazzband/pip-tools?tab=readme-ov-file#updating-requirements).
2024-02-20 17:44:15 +00:00

169 lines
3.9 KiB
Text

#
# This file is autogenerated by pip-compile with Python 3.11
# by the following command:
#
# pip-compile --strip-extras ./engine/requirements-dev.in
#
asgiref==3.7.2
# via
# -c ./engine/requirements.txt
# django
celery-types==0.18.0
# via -r ./engine/requirements-dev.in
certifi==2024.2.2
# via
# -c ./engine/requirements.txt
# requests
cfgv==3.4.0
# via pre-commit
charset-normalizer==3.3.2
# via
# -c ./engine/requirements.txt
# requests
distlib==0.3.8
# via virtualenv
django==4.2.10
# via
# -c ./engine/requirements.txt
# django-stubs
# django-stubs-ext
django-filter-stubs==0.1.3
# via -r ./engine/requirements-dev.in
django-stubs==4.2.2
# via
# -r ./engine/requirements-dev.in
# django-filter-stubs
# django-stubs
# djangorestframework-stubs
django-stubs-ext==4.2.7
# via django-stubs
djangorestframework-stubs==3.14.2
# via
# -r ./engine/requirements-dev.in
# django-filter-stubs
# djangorestframework-stubs
execnet==2.0.2
# via pytest-xdist
factory-boy==2.12.0
# via
# -c ./engine/requirements.txt
# pytest-factoryboy
faker==23.1.0
# via
# -c ./engine/requirements.txt
# factory-boy
filelock==3.13.1
# via virtualenv
httpretty==1.1.4
# via -r ./engine/requirements-dev.in
identify==2.5.34
# via pre-commit
idna==3.6
# via
# -c ./engine/requirements.txt
# requests
inflection==0.5.1
# via
# -c ./engine/requirements.txt
# pytest-factoryboy
iniconfig==2.0.0
# via pytest
mypy==1.4.1
# via
# -r ./engine/requirements-dev.in
# django-filter-stubs
# django-stubs
# djangorestframework-stubs
mypy-extensions==1.0.0
# via mypy
nodeenv==1.8.0
# via pre-commit
packaging==23.2
# via pytest
platformdirs==4.2.0
# via virtualenv
pluggy==1.4.0
# via pytest
pre-commit==2.15.0
# via -r ./engine/requirements-dev.in
psutil==5.9.4
# via
# -c ./engine/requirements.txt
# pytest-xdist
pytest==7.3.1
# via
# -r ./engine/requirements-dev.in
# pytest-django
# pytest-factoryboy
# pytest-xdist
pytest-django==4.5.2
# via -r ./engine/requirements-dev.in
pytest-factoryboy==2.5.1
# via -r ./engine/requirements-dev.in
pytest-xdist==3.5.0
# via
# -r ./engine/requirements-dev.in
# pytest-xdist
python-dateutil==2.8.2
# via
# -c ./engine/requirements.txt
# faker
pyyaml==6.0.1
# via
# -c ./engine/requirements.txt
# pre-commit
requests==2.31.0
# via
# -c ./engine/requirements.txt
# djangorestframework-stubs
six==1.16.0
# via
# -c ./engine/requirements.txt
# python-dateutil
sqlparse==0.4.4
# via
# -c ./engine/requirements.txt
# django
toml==0.10.2
# via
# -c ./engine/requirements.txt
# pre-commit
types-beautifulsoup4==4.12.0.5
# via -r ./engine/requirements-dev.in
types-html5lib==1.1.11.20240106
# via types-beautifulsoup4
types-pymysql==1.0.19.7
# via -r ./engine/requirements-dev.in
types-python-dateutil==2.8.19.13
# via -r ./engine/requirements-dev.in
types-pytz==2024.1.0.20240203
# via django-stubs
types-pyyaml==6.0.12.12
# via
# django-stubs
# djangorestframework-stubs
types-requests==2.31.0.1
# via
# -r ./engine/requirements-dev.in
# djangorestframework-stubs
types-urllib3==1.26.25.14
# via types-requests
typing-extensions==4.9.0
# via
# -c ./engine/requirements.txt
# celery-types
# django-filter-stubs
# django-stubs
# django-stubs-ext
# djangorestframework-stubs
# mypy
# pytest-factoryboy
urllib3==1.26.18
# via
# -c ./engine/requirements.txt
# requests
virtualenv==20.25.0
# via pre-commit
# The following packages are considered to be unsafe in a requirements file:
# setuptools