1
0
mirror of https://github.com/etesync/server synced 2024-11-22 08:48:07 +00:00
etesync-server/requirements-dev.txt
Victor R. Santos e0010f21f6
Update dependecies generated by pip-compile. (#126)
This one is to fix my own PR #125, the requirement files contained the following sentence:

"To update, run: pip-compile --output-file=requirements.txt requirements.in/base.txt"

But that was misleading, after reading pip-tools documentation I found that

"If pip-compile finds an existing requirements.txt file that fulfils the dependencies then no changes will be made, even if updates are available."

That was my mistake, generated the files again and made new builds using python 3.10 that worked as expected. Once again sorry for the mistake!
2022-03-23 11:36:21 +02:00

68 lines
1.4 KiB
Plaintext

#
# This file is autogenerated by pip-compile with python 3.10
# To update, run:
#
# pip-compile --output-file=requirements-dev.txt requirements.in/development.txt
#
asgiref==3.5.0
# via django
black==22.1.0
# via -r requirements.in/development.txt
click==8.0.4
# via
# black
# pip-tools
coverage==6.3.2
# via -r requirements.in/development.txt
django==3.2.12
# via
# -r requirements.in/development.txt
# django-stubs
# django-stubs-ext
django-stubs==1.9.0
# via -r requirements.in/development.txt
django-stubs-ext==0.3.1
# via django-stubs
mypy==0.941
# via django-stubs
mypy-extensions==0.4.3
# via
# black
# mypy
pathspec==0.9.0
# via black
pep517==0.12.0
# via pip-tools
pip-tools==6.5.1
# via -r requirements.in/development.txt
platformdirs==2.5.1
# via black
pytz==2022.1
# via django
pywatchman==1.4.1
# via -r requirements.in/development.txt
sqlparse==0.4.2
# via django
toml==0.10.2
# via django-stubs
tomli==2.0.1
# via
# black
# mypy
# pep517
types-pytz==2021.3.6
# via django-stubs
types-pyyaml==6.0.5
# via django-stubs
typing-extensions==4.1.1
# via
# django-stubs
# django-stubs-ext
# mypy
wheel==0.37.1
# via pip-tools
# The following packages are considered to be unsafe in a requirements file:
# pip
# setuptools