Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/requirements/dev.txt

179 lines
5.5 KiB
Plaintext
Raw Normal View History

requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
#
# This file is GENERATED. Don't edit directly.
#
# To update, edit the non-"lock" files in requirements/*.txt, then:
#
# tools/update-locked-requirements
#
# For details, see requirements/README.md .
#
git+https://github.com/zulip/talon.git@7d8bdc4dbcfcc5a73298747293b99fe53da55315#egg=talon==1.2.10.zulip1
git+https://github.com/zulip/ultrajson@70ac02bec#egg=ujson==1.35+git
git+https://github.com/zulip/virtualenv-clone.git@44e831da39ffb6b9bb5c7d103d98babccdca0456#egg=virtualenv-clone==0.2.6.zulip1
pypi_packages: Upgrade to release 0.4.1.
2018-02-07 05:38:44 +01:00
git+https://github.com/zulip/python-zulip-api.git@0.4.1#egg=zulip==0.4.1_git&subdirectory=zulip
git+https://github.com/zulip/python-zulip-api.git@0.4.1#egg=zulip_bots==0.4.1+git&subdirectory=zulip_bots
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
alabaster==0.7.10
apns2==0.3.0
requirements: Upgrade argon2-cffi to 18.1.0.
2018-02-13 19:16:31 +01:00
argon2-cffi==18.1.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
arrow==0.10.0 # via gitlint
asn1crypto==0.23.0 # via cryptography
attrs==17.3.0 # via automat, service-identity
automat==0.6.0 # via twisted
aws-xray-sdk==0.94 # via moto
requirements: Upgrade Babel to 2.5.3.
2018-02-13 19:26:25 +01:00
babel==2.5.3
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
backports-abc==0.5
backports.ssl-match-hostname==3.5.0.1
beautifulsoup4==4.6.0
boto3==1.4.7 # via moto
boto==2.48.0
botocore==1.7.46 # via boto3, moto, s3transfer
cchardet==2.1.1
requirements: Upgrade certifi to 2018.1.18.
2018-02-14 09:55:24 +01:00
certifi==2018.1.18
requirements: Upgrade cffi to 1.11.4.
2018-02-13 19:35:42 +01:00
cffi==1.11.4
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
chardet==3.0.4
click==6.6 # via gitlint, pip-tools
commonmark==0.5.4
constantly==15.1.0 # via twisted
cookies==2.2.1 # via moto
requirements: Upgrade cryptography to 2.1.4.
2018-02-13 19:51:53 +01:00
coverage==4.5.1
cryptography==2.1.4
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
cssselect==1.0.1 # via parsel, premailer, scrapy
cssutils==1.0.2 # via premailer
decorator==4.1.2 # via ipython, traitlets
defusedxml==0.5.0
django-auth-ldap==1.2.16
django-bitfield==1.9.3
requirements: Add dependencies for two-factor auth. We're not yet ready to add 2FA to Zulip yet, but we've determined we'd like to work from these libraries. I'm not bothering to bump PROVISION_VERSION for this, since we're likely to do something else that bumps it soon, and we're not merging anything that uses these new libraries.
2017-11-29 00:13:09 +01:00
django-formtools==2.1 # via django-two-factor-auth
django-otp==0.4.1.1 # via django-two-factor-auth
django-phonenumber-field==1.3.0 # via django-two-factor-auth
requirements: Upgrade django-pipeline to 1.6.14.
2018-02-13 20:02:59 +01:00
django-pipeline==1.6.14
local-uploads: Start running authentication checks on file requests. From here on we start to authenticate uploaded file request before serving this files in production. This involves allowing NGINX to pass on these file requests to Django for authentication and then serve these files by making use on internal redirect requests having x-accel-redirect field. The redirection on requests and loading of x-accel-redirect param is handled by django-sendfile. NOTE: This commit starts to authenticate these requests for Zulip servers running platforms either Ubuntu Xenial (16.04) or above. Fixes: #320 and #291 partially.
2018-02-12 18:18:03 +01:00
django-sendfile==0.3.11
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
django-statsd-mozilla==0.4.0
requirements: Upgrade django-two-factor-auth to 1.7.0.
2018-02-13 20:06:07 +01:00
django-two-factor-auth==1.7.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
django-webpack-loader==0.5.0
django==1.11.6
docker-pycreds==0.2.1 # via docker
docker==2.6.1 # via moto
docopt==0.6.2
docutils==0.14
requirements: Upgrade to fakeldap 0.6.1. Tweaked by tabbott to remove the unnecessary GitHub indirection.
2017-11-11 01:02:56 +01:00
fakeldap==0.6.1
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
first==2.0.1 # via pip-tools
gitdb==0.6.4
requirements: Upgrade gitlint to 0.9.0.
2018-02-13 20:08:44 +01:00
gitlint==0.9.0
requirements: Upgrade google-api-python-client to 1.6.5.
2018-02-14 11:21:12 +01:00
google-api-python-client==1.6.5
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
h2==2.6.2 # via hyper
hpack==3.0.0 # via h2
requirements: Upgrade html2text to 2018.1.9.
2018-02-13 20:10:51 +01:00
html2text==2018.1.9
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
httplib2==0.10.3
hyper==0.7.0 # via apns2
hyperframe==3.2.0 # via h2, hyper
hyperlink==17.3.1 # via twisted
idna==2.6 # via cryptography, requests
ijson==2.3
imagesize==0.7.1
incremental==17.5.0 # via twisted
ipython-genutils==0.2.0 # via traitlets
ipython==6.2.1
requirements: Upgrade isort to 4.3.4.
2018-02-13 20:22:04 +01:00
isort==4.3.4
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
jedi==0.11.0 # via ipython
requirements: Upgrade Jinja2 to 2.10.
2018-02-13 20:24:45 +01:00
jinja2==2.10
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
jmespath==0.9.3 # via boto3, botocore
requirements: Upgrade moto to 1.2.0.
2018-02-13 20:33:55 +01:00
jsondiff==1.1.1 # via moto
requirements: Upgrade python-digital-ocean to 1.13.2.
2018-02-14 11:35:54 +01:00
jsonpickle==0.9.5 # via aws-xray-sdk, python-digitalocean
requirements: Upgrade lxml to 4.1.1.
2018-02-13 20:27:50 +01:00
lxml==4.1.1
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
markdown-include==0.5.1
requirements: Upgrade Markdown to 2.6.11.
2018-02-13 20:31:09 +01:00
markdown==2.6.11
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
markupsafe==1.0
mock==2.0.0
requirements: Upgrade moto to 1.2.0.
2018-02-13 20:33:55 +01:00
moto==1.2.0
requirements: Upgrade mypy to 0.560. Fixes #7835.
2017-12-20 00:44:28 +01:00
mypy==0.560
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
mypy_extensions==0.3.0
requirements: Upgrade ndg-httpsclient to 0.4.4.
2018-02-14 11:23:09 +01:00
ndg-httpsclient==0.4.4
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
oauth2client==4.1.2
oauthlib==2.0.6
ordereddict==1.1 # via gitlint
requirements: Upgrade Sphinx to 1.7.0.
2018-02-13 21:30:29 +01:00
packaging==16.8 # via sphinx
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
parsel==1.2.0 # via scrapy
parso==0.1.0 # via jedi
pbr==3.1.1 # via mock
pexpect==4.3.0 # via ipython
requirements: Add dependencies for two-factor auth. We're not yet ready to add 2FA to Zulip yet, but we've determined we'd like to work from these libraries. I'm not bothering to bump PROVISION_VERSION for this, since we're likely to do something else that bumps it soon, and we're not merging anything that uses these new libraries.
2017-11-29 00:13:09 +01:00
phonenumberslite==8.8.6 # via django-phonenumber-field
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
pickleshare==0.7.4 # via ipython
requirements: Upgrade pika to 0.11.2.
2018-02-13 20:42:03 +01:00
pika==0.11.2
requirements: Upgrade Pillow to 5.0.0.
2018-02-13 20:44:37 +01:00
pillow==5.0.0
requirements: Upgrade pip-tools to 1.11.0.
2018-02-13 20:46:47 +01:00
pip-tools==1.11.0
requirements: Upgrade polib to 1.1.0.
2018-02-13 20:53:36 +01:00
polib==1.1.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
premailer==3.1.1
prompt-toolkit==1.0.15 # via ipython
requirements: Upgrade mypy to 0.550. We have to add a few type: ignores due to mypy 0.550 having some bugs in the new imaplib stubs in typeshed. Fixes #7387.
2017-11-24 23:26:44 +01:00
psutil==5.4.1 # via mypy
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
psycopg2==2.7.3.2
ptyprocess==0.5.2 # via pexpect
py3dns==3.1.0
pyaml==17.10.0 # via moto
requirements: Upgrade pyasn1 to pyasn1-modules.
2018-02-13 21:03:51 +01:00
pyasn1-modules==0.2.1
pyasn1==0.4.2
Lock the recursive requirements in dev.txt via pip-compile. First, all the lines of py3_dev.txt except for mypy.txt are mv-ed to dev.txt. Then dev_lock.txt is generated from dev.txt to be used by py3_dev.txt. `click` is removed from moto.txt since it is already a dependency of several libraries and will appear as an autogenerated dependency.
2017-08-22 02:26:16 +02:00
pycodestyle==2.3.1
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
pycparser==2.18 # via cffi
pycrypto==2.6.1
pydispatcher==2.0.5 # via scrapy
Lock the recursive requirements in dev.txt via pip-compile. First, all the lines of py3_dev.txt except for mypy.txt are mv-ed to dev.txt. Then dev_lock.txt is generated from dev.txt to be used by py3_dev.txt. `click` is removed from moto.txt since it is already a dependency of several libraries and will appear as an autogenerated dependency.
2017-08-22 02:26:16 +02:00
pyflakes==1.6.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
pygments==2.2.0
pyjwt==1.5.3
pyldap==2.4.37
pylibmc==1.5.2
pyoembed==0.1.2
pyopenssl==17.3.0 # via ndg-httpsclient, scrapy, service-identity
requirements: Upgrade Sphinx to 1.7.0.
2018-02-13 21:30:29 +01:00
pyparsing==2.2.0 # via packaging
requirements: Add dependencies for two-factor auth. We're not yet ready to add 2FA to Zulip yet, but we've determined we'd like to work from these libraries. I'm not bothering to bump PROVISION_VERSION for this, since we're likely to do something else that bumps it soon, and we're not merging anything that uses these new libraries.
2017-11-29 00:13:09 +01:00
pysocks==1.6.7 # via twilio
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
python-dateutil==2.6.1
requirements: Upgrade python-digital-ocean to 1.13.2.
2018-02-14 11:35:54 +01:00
python-digitalocean==1.13.2
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
python-gcm==0.4
python-twitter==3.3
python3-openid==3.1.0 # via social-auth-core
requirements: Upgrade pytz to 2018.3.
2018-02-13 21:11:04 +01:00
pytz==2018.3
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
pyyaml==3.12 # via pyaml
requirements: Add dependencies for two-factor auth. We're not yet ready to add 2FA to Zulip yet, but we've determined we'd like to work from these libraries. I'm not bothering to bump PROVISION_VERSION for this, since we're likely to do something else that bumps it soon, and we're not merging anything that uses these new libraries.
2017-11-29 00:13:09 +01:00
qrcode==4.0.4 # via django-two-factor-auth
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
queuelib==1.4.2 # via scrapy
recommonmark==0.4.0
redis==2.10.6
regex==2017.11.9
requests-oauthlib==0.8.0
requirements: Include stripe in common.in.
2018-01-13 19:36:21 +01:00
requests==2.18.4 # via aws-xray-sdk, docker, moto, premailer, pyoembed, python-digitalocean, python-gcm, python-twitter, requests-oauthlib, social-auth-core, sphinx, stripe, twilio
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
rsa==3.4.2
s3transfer==0.1.11 # via boto3
requirements: Upgrade Scrapy to 1.5.0.
2018-02-13 21:14:57 +01:00
scrapy==1.5.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
service-identity==17.0.0 # via scrapy
sh==1.11 # via gitlint
simplegeneric==0.8.1 # via ipython
six==1.11.0
smmap==0.9.0
profiling: Add snakeviz to dev tools. This adds snakeviz to dev tools and also updates the message displayed upon running `test-backend` with `--profile` option to say how to run snakeviz correctly when using vagrant development environment.
2017-09-04 14:35:08 +02:00
snakeviz==0.4.2
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
snowballstemmer==1.2.1
django-2.0: Bump social auth version to 2.1.0.
2018-01-30 10:35:13 +01:00
social-auth-app-django==2.1.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
social-auth-core==1.5.0 # via social-auth-app-django
sockjs-tornado==1.0.3
sourcemap==0.2.1
sphinx-rtd-theme==0.2.4
requirements: Upgrade Sphinx to 1.7.0.
2018-02-13 21:30:29 +01:00
sphinx==1.7.0
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
sphinxcontrib-websupport==1.0.1 # via sphinx
sqlalchemy==1.1.14
statsd==3.2.1 # via django-statsd-mozilla
requirements: Upgrade stripe to 1.77.2.
2018-02-13 21:36:48 +01:00
stripe==1.77.2
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
tblib==1.3.2
requirements: Upgrade tornado to 4.5.3.
2018-02-13 21:44:35 +01:00
tornado==4.5.3
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
traitlets==4.3.2 # via ipython
requirements: Upgrade transifex-client to 0.12.5.
2018-02-14 09:13:32 +01:00
transifex-client==0.12.5
requirements: Upgrade twilio to two.
2018-02-14 09:16:11 +01:00
twilio==6.10.3
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
twisted==17.9.0
typed-ast==1.1.0 # via mypy
requirements: Upgrade typing to 3.6.4.
2018-02-13 21:41:16 +01:00
typing==3.6.4
requirements: Rename requirements files. This commit renames various source requirements files like `dev.txt`, `mypy.txt` etc to `dev.in`, `mypy.in` etc and various locked requirements files like `dev_lock.txt`, `mypy_lock.txt` etc to `dev.txt`, `mypy.txt` etc. This will help in emphasizing to the user that *.in are actually input to `update-locked-requirements` tool which should be run after updating any of these.
2017-11-17 02:41:06 +01:00
uritemplate==3.0.0
urllib3==1.22 # via requests, transifex-client
w3lib==1.18.0 # via parsel, scrapy
wcwidth==0.1.7 # via prompt-toolkit
websocket-client==0.44.0 # via docker
werkzeug==0.12.2 # via moto
wrapt==1.10.11 # via aws-xray-sdk
xmltodict==0.11.0 # via moto
zope.interface==4.4.3 # via twisted