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

126 lines
3.7 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 .
#
requirements: Upgrade psycopg2 to 2.7.3.4. psycopg2 package contains both binary and source currently.The binary would soon be only available in psycopg2-binary. So currently installing psycopg2 will show a warning about the future migration of binary. To avoid the warning we should only install the source. https://www.postgresql.org/message-id/CA%2Bmi_8bd6kJHL TGkuyHSnqcgDrJ1uHgQWvXCKQFD3tPQBUa2Bw%40mail.gmail.com
2018-02-21 08:08:30 +01:00
--no-binary psycopg2
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
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
pypi: Upgrade to release 0.4.7.
2018-05-22 00:55:42 +02:00
git+https://github.com/zulip/python-zulip-api.git@0.4.7#egg=zulip==0.4.7_git&subdirectory=zulip
zulip_bots: Upgrade to latest commit. This upgrade fixes a dependency conflict between one of the bots in zulip_bots and the main repo.
2018-06-05 00:53:10 +02:00
git+https://github.com/zulip/python-zulip-api.git@e7e9059cb812914d2760bdb6c5032d17d95ee8df#egg=zulip_bots==0.4.7+git&subdirectory=zulip_bots
requirements: Upgrade apns to 0.4.1.
2018-05-24 13:05:23 +02:00
apns2==0.4.1
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
asn1crypto==0.23.0 # via cryptography
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
babel==2.5.1 # via django-phonenumber-field
requirements: Upgrade ipython to 6.3.1.
2018-05-02 18:28:16 +02:00
backcall==0.1.0 # via ipython
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
boto==2.48.0
cchardet==2.1.1
requirements: Upgrade certifi to 2018.1.18.
2018-05-03 21:36:49 +02:00
certifi==2018.4.16
requirements: Upgrade cffi to 1.11.5.
2018-04-01 17:10:05 +02:00
cffi==1.11.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
chardet==3.0.4
requirements: Upgrade cryptography to 2.2.2.
2018-04-01 17:11:42 +02:00
cryptography==2.2.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
cssselect==1.0.1 # via premailer
cssutils==1.0.2 # via premailer
decorator==4.1.2 # via ipython, traitlets
defusedxml==0.5.0
requirements: Upgrade disposable-email-domains to 0.0.28.
2018-05-24 13:08:24 +02:00
disposable-email-domains==0.0.28
ldap: Make Zulip compatible with django-auth-ldap==1.5. In version 1.5, get_or_create_user method is not used. It exists just for the compatibility. The main function to use now is get_or_build_user. See the changelog: https://django-auth-ldap.readthedocs.io/en/latest/changes.html#id1 Fixes #9307
2018-05-22 08:33:56 +02:00
django-auth-ldap==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
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: Upgrade django-webpack-loader to 0.6.0.
2018-04-01 15:04:08 +02:00
django-webpack-loader==0.6.0
requirements: Upgrade Django to 1.11.13.
2018-05-28 14:41:04 +02:00
django==1.11.13
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
docopt==0.6.2
gitdb==0.6.4
requirements: Upgrade google-api-python-client to 1.6.7.
2018-05-02 18:25:59 +02:00
google-api-python-client==1.6.7
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: Upgrade httplib2 to 0.11.3.
2018-04-01 15:08:04 +02:00
httplib2==0.11.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
hyper==0.7.0 # via apns2
hyperframe==3.2.0 # via h2, hyper
idna==2.6 # via cryptography, requests
ijson==2.3
ipython-genutils==0.2.0 # via traitlets
requirements: Upgrade ipython to 6.4.0.
2018-05-24 13:12:24 +02:00
ipython==6.4.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
jedi==0.11.0 # via ipython
requirements: Upgrade Jinja2 to 2.10.
2018-02-13 20:24:45 +01:00
jinja2==2.10
requirements: Upgrade lxml to 4.2.1.
2018-04-01 17:13:09 +02:00
lxml==4.2.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
mypy_extensions==0.3.0
requirements: Upgrade ndg-httpsclient to 0.5.0.
2018-05-02 18:39:32 +02:00
ndg-httpsclient==0.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
oauth2client==4.1.2
requirements: Upgrade oauthlib to 2.1.0.
2018-05-24 13:14:17 +02:00
oauthlib==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
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: Downgrade pika to 0.11.0. Downgrading as issue #8466 is not fixed yet.
2018-04-11 08:34:53 +02:00
pika==0.11.0
requirements: Upgrade Pillow to 5.1.0.
2018-05-02 18:43:30 +02:00
pillow==5.1.0
requirements: Upgrade polib to 1.1.0.
2018-02-13 20:53:36 +01:00
polib==1.1.0
requirements: Upgrade premailer to 3.2.0.
2018-05-02 19:26:56 +02:00
premailer==3.2.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
prompt-toolkit==1.0.15 # via ipython
requirements: Upgrade psycopg2 to 2.7.3.4. psycopg2 package contains both binary and source currently.The binary would soon be only available in psycopg2-binary. So currently installing psycopg2 will show a warning about the future migration of binary. To avoid the warning we should only install the source. https://www.postgresql.org/message-id/CA%2Bmi_8bd6kJHL TGkuyHSnqcgDrJ1uHgQWvXCKQFD3tPQBUa2Bw%40mail.gmail.com
2018-02-21 08:08:30 +01:00
psycopg2==2.7.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
ptyprocess==0.5.2 # via pexpect
py3dns==3.1.0
requirements: Upgrade pyasn1 to pyasn1-modules.
2018-02-13 21:03:51 +01:00
pyasn1-modules==0.2.1
requirements: Upgrade pyasn1 to 0.4.3.
2018-05-24 13:31:27 +02:00
pyasn1==0.4.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
pycparser==2.18 # via cffi
pycrypto==2.6.1
pygments==2.2.0
requirements: Upgrade PyJWT to 1.6.4.
2018-05-24 21:47:19 +02:00
pyjwt==1.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
pylibmc==1.5.2
pyoembed==0.1.2
zulip_bots: Upgrade to latest commit. This upgrade fixes a dependency conflict between one of the bots in zulip_bots and the main repo.
2018-06-05 00:53:10 +02:00
pyopenssl==17.3.0 # via ndg-httpsclient, requests
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
python-gcm==0.4
ldap: Make Zulip compatible with django-auth-ldap==1.5. In version 1.5, get_or_create_user method is not used. It exists just for the compatibility. The main function to use now is get_or_build_user. See the changelog: https://django-auth-ldap.readthedocs.io/en/latest/changes.html#id1 Fixes #9307
2018-05-22 08:33:56 +02:00
python-ldap==3.0.0 # via django-auth-ldap
requirements: Upgrade python-twitter to 3.4.1.
2018-04-02 08:29:08 +02:00
python-twitter==3.4.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
python3-openid==3.1.0 # via social-auth-core
requirements: Upgrade pytz to 2018.4.
2018-05-24 17:02:05 +02:00
pytz==2018.4
requirements: Add dependency for parsing OpenAPI-formatted YAML files.
2018-05-26 00:59:35 +02:00
pyyaml==3.12 # via yamole
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
redis==2.10.6
regex==2017.11.9
requests-oauthlib==0.8.0
zulip_bots: Upgrade to latest commit. This upgrade fixes a dependency conflict between one of the bots in zulip_bots and the main repo.
2018-06-05 00:53:10 +02:00
requests[security]==2.18.4 # via premailer, pyoembed, python-gcm, python-twitter, requests-oauthlib, social-auth-core, 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
simplegeneric==0.8.1 # via ipython
six==1.11.0
smmap==0.9.0
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
requirements: Upgrade SQLAlchemy to 1.2.7.
2018-05-02 19:46:31 +02:00
sqlalchemy==1.2.7
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
statsd==3.2.1 # via django-statsd-mozilla
requirements: Upgrade stripe to 1.82.1.
2018-05-24 18:20:23 +02:00
stripe==1.82.1
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 twilio to 6.14.0.
2018-05-24 18:18:04 +02:00
twilio==6.14.0
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
requirements: Update uwsgi to the latest version. Apparently, older uwsgi doesn't install properly on systems with newer versions of OpenSSL; see https://github.com/unbit/uwsgi/issues/1395 for details. This fixes #7609.
2018-03-06 22:11:00 +01:00
uwsgi==2.0.17
requirements: Upgrade to virtualenv-clone 0.3.0.
2018-03-02 23:54:22 +01:00
virtualenv-clone==0.3.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
wcwidth==0.1.7 # via prompt-toolkit
tests: Allow testing our REST API against the OpenAPI docs.
2018-05-31 19:41:17 +02:00
yamole==2.1.2