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

196 lines
6.3 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
Fork django-bitfield to save a few hundred ms of startup time See #9953, https://github.com/zulip/django-bitfield/pull/1. Signed-off-by: Anders Kaseorg <andersk@mit.edu>
2018-07-18 21:18:38 +02:00
git+https://github.com/zulip/django-bitfield@0d2b15cdb5af5ddec88d41cac19c0f2ce1b1ad38#egg=django-bitfield==1.9.3+dev.0d2b15cdb5af5ddec88d41cac19c0f2ce1b1ad38
requirements: Use a forked version of libthumbor for performance. This optimizes the import performance of Zulip by using a fork of pkgresources. The fork just has a single commit, which replaces libthumbor's use of pkgresources (which is really slow to import) with a direct query to the version number. This fixes part of #9953.
2018-10-17 20:15:02 +02:00
git+https://github.com/zulip/libthumbor.git@60ed2431c07686a12f2770b2d852c5650f3ccfc6#egg=libthumbor==1.3.2zulip
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
python-zulip-api: Upgrade to latest PyPI release (0.5.6).
2018-12-17 22:33:09 +01:00
git+https://github.com/zulip/python-zulip-api.git@0.5.6#egg=zulip==0.5.6_git&subdirectory=zulip
git+https://github.com/zulip/python-zulip-api.git@0.5.6#egg=zulip_bots==0.5.6+git&subdirectory=zulip_bots
requirements: Upgrade albaster to 0.7.12.
2018-11-09 07:31:21 +01:00
alabaster==0.7.12
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.3.0.
2018-11-09 07:32:51 +01:00
argon2-cffi==18.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
arrow==0.10.0 # via gitlint
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
asn1crypto==0.24.0 # via cryptography
requirements: Upgrade Twisted to 18.9.0.
2018-11-12 07:55:13 +01:00
attrs==18.2.0 # via automat, service-identity, twisted
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
automat==0.7.0 # via twisted
aws-xray-sdk==0.95 # via moto
requirements: Upgrade Babel to 2.5.3.
2018-02-13 19:26:25 +01:00
babel==2.5.3
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
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
beautifulsoup4==4.7.1
boto3==1.9.74 # via moto
requirements: Upgrade boto to 2.49.0. Updated the CA Bundle as well as some bucket encryption fixes.
2018-07-30 10:58:12 +02:00
boto==2.49.0
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
botocore==1.12.74 # via boto3, moto, s3transfer
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
cachetools==3.0.0 # via google-auth
cchardet==2.1.4
requirements: Upgrade certifi from 2018.10.15 to 2018.11.29.
2019-01-07 08:53:52 +01:00
certifi==2018.11.29
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
click==6.6 # via gitlint, pip-tools
commonmark==0.5.4
constantly==15.1.0 # via twisted
requirements: Upgrade coverage to 4.5.2.
2018-11-13 07:52:36 +01:00
coverage==4.5.2
requirements: Upgrade cryptography from 2.4.1 to 2.4.2.
2019-01-07 08:57:09 +01:00
cryptography==2.4.2
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
cssselect==1.0.3 # via parsel, premailer, scrapy
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
cssutils==1.0.2 # via premailer
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
decorator==4.3.0 # via ipython, traitlets
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
defusedxml==0.5.0
requirements: Upgrade disposable-email-domains from 0.0.38 to 0.0.39.
2019-01-07 09:00:37 +01:00
disposable-email-domains==0.0.39
requirements: Upgrade django-auth-ldap to 1.7.0.
2018-11-12 08:26:02 +01:00
django-auth-ldap==1.7.0
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
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
django-otp==0.5.1 # via django-two-factor-auth
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-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
django-pylibmc: Add dependancy and use as cache backend for memcached.
2018-06-11 04:19:16 +02:00
django-pylibmc==0.6.1
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.8.0.
2018-11-09 07:53:03 +01:00
django-two-factor-auth==1.8.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.18.
2019-01-07 17:37:11 +01:00
django==1.11.18
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
docker-pycreds==0.4.0 # via docker
docker==3.6.0 # via moto
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
docutils==0.14
requirements: Upgrade moto from 1.3.3 to 1.3.7.
2019-01-07 09:34:11 +01:00
ecdsa==0.13 # via python-jose
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.10.0.
2018-05-03 21:37:45 +02:00
gitlint==0.10.0
requirements: Upgrade google-api-python-client to 1.7.4. Mostly cleanups. Also updated to catch ServerNotFoundError and retry the request.
2018-07-30 12:10:58 +02:00
google-api-python-client==1.7.4
google-auth-httplib2==0.0.3 # via google-api-python-client
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
google-auth==1.6.2 # via google-api-python-client, google-auth-httplib2
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 from 0.11.3 to 0.12.0.
2019-01-07 09:19:38 +01:00
httplib2==0.12.0
requirements: Upgrade httpretty to 0.9.6.
2018-11-09 11:17:11 +01:00
httpretty==0.9.6
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
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
hyperlink==18.0.0 # via twisted
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
idna==2.8 # via cryptography, hyperlink, requests
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
ijson==2.3
requirements: Upgrade imagesize to 1.1.0.
2018-11-09 11:18:38 +01:00
imagesize==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
incremental==17.5.0 # via twisted
ipython-genutils==0.2.0 # via traitlets
requirements: Upgrade ipython to 6.5.0. No major changes. Miscellaneous bug fixes and compatibility with Python 3.7.
2018-07-30 12:39:26 +02:00
ipython==6.5.0
requirements: Upgrade isort to 4.3.4.
2018-02-13 20:22:04 +01:00
isort==4.3.4
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
jedi==0.13.2 # 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: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
jsonpickle==1.0 # via aws-xray-sdk, python-digitalocean
requirements: Upgrade lxml from 4.2.5 to 4.3.0.
2019-01-07 09:30:39 +01:00
lxml==4.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
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: Upgrade Markupsafe to 1.1.0.
2018-11-09 11:22:53 +01:00
markupsafe==1.1.0
requirements: Upgrade python-zulip-api/zulip to 7dfecf557.
2018-08-15 11:34:45 +02:00
matrix-client==0.3.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
mock==2.0.0
requirements: Upgrade moto from 1.3.3 to 1.3.7.
2019-01-07 09:34:11 +01:00
moto==1.3.7
dependencies: Upgrade mypy to version 0.641. This requires upgrading a few other packages that mypy depends on.
2018-10-19 23:06:16 +02:00
mypy-extensions==0.4.1
dependencies: Upgrade mypy to version 0.650. Broaden the type of the AbstractEnum __reduce_ex__ parameter to object; this matches the parameter type specified in the latest enum.pyi file in typeshed. Fixes #10996.
2018-12-08 18:20:39 +01:00
mypy==0.650
requirements: Upgrade ndg-httpsclient to 0.5.1. Some minor changes. * Clean up handling for description file - pull in content from this file into setup() * Allows the nightly build to fail * Add Trove version classifiers to make it explicit what is supported * Add python_requires to help pip * Drop support for EOL Python 2.6 and 3.3
2018-07-30 12:49:32 +02:00
ndg-httpsclient==0.5.1
requirements: Upgrade oauth2client to 4.1.3.
2018-11-09 11:24:17 +01:00
oauth2client==4.1.3
requirements: Upgrade oauthlib to 2.1.0.
2018-05-24 13:14:17 +02:00
oauthlib==2.1.0
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
packaging==18.0 # via sphinx
parsel==1.5.1 # via scrapy
parso==0.3.1 # via jedi
pbr==5.1.1 # via mock
pexpect==4.6.0 # via ipython
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
phonenumberslite==8.10.2 # via django-phonenumber-field
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
pickleshare==0.7.5 # via ipython
requirements: Upgrade pika from 0.11.0 to 0.12.0. Based on our analysis, the bug that made us uncomfortable with upgrading to 0.11.2 was fixed in 0.12.0. Fixes #8466.
2019-01-07 09:37:36 +01:00
pika==0.12.0
requirements: Upgrade Pillow from 5.3.0 to 5.4.1.
2019-01-07 09:41:02 +01:00
pillow==5.4.1
requirements: Upgrade pip-tools to 2.0.2.
2018-05-02 18:46:25 +02:00
pip-tools==2.0.2
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.6.1.
2018-11-12 08:50:26 +01:00
psycopg2==2.7.6.1
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
ptyprocess==0.6.0 # via pexpect
requirements: Upgrade py3dns to 3.2.0. A bunch of minor bug fixes.
2018-07-30 13:17:57 +02:00
py3dns==3.2.0
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
pyaml==18.11.0 # via moto
requirements: Upgrade pyasn1-modules from 0.2.2 to 0.2.3.
2019-01-07 11:52:20 +01:00
pyasn1-modules==0.2.3
requirements: Upgrade pyasn1 from 0.4.4 to 0.4.5.
2019-01-07 11:47:51 +01:00
pyasn1==0.4.5
tools: Upgrade pycodestyle. We have to add a few rules that we're ignoring for now.
2018-05-14 03:31:47 +02:00
pycodestyle==2.4.0
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
pycparser==2.19 # via cffi
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
pycrypto==2.6.1
requirements: Upgrade moto from 1.3.3 to 1.3.7.
2019-01-07 09:34:11 +01:00
pycryptodome==3.7.2 # via python-jose
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
pydispatcher==2.0.5 # via scrapy
requirements: Upgrade pyflakes to 2.0.0. We fix a few errors that only the new version finds.
2018-05-24 16:41:34 +02:00
pyflakes==2.0.0
requirements: Upgrade Pygments from 2.2.0 to 2.3.1.
2019-01-07 11:55:47 +01:00
pygments==2.3.1
requirements: Upgrade Twisted to 18.9.0.
2018-11-12 07:55:13 +01:00
pyhamcrest==1.9.0 # via twisted
requirements: Upgrade PyJWT from 1.6.4 to 1.7.1.
2019-01-07 11:59:17 +01:00
pyjwt==1.7.1
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
pyldap==3.0.0.post1 # via fakeldap
requirements: Upgrade pylibmc to 1.6.0.
2018-11-12 08:51:28 +01:00
pylibmc==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
pyoembed==0.1.2
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
pyopenssl==18.0.0 # via ndg-httpsclient, requests, scrapy
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
pyparsing==2.3.0 # via packaging
pysocks==1.6.8 # via twilio
requirements: Upgrade python-dateutil from 2.6.1 to 2.7.5.
2019-01-07 12:03:00 +01:00
python-dateutil==2.7.5
requirements: Upgrade python-digital-ocean to 1.14.0.
2018-11-09 16:11:57 +01:00
python-digitalocean==1.14.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
python-gcm==0.4
requirements: Upgrade moto from 1.3.3 to 1.3.7.
2019-01-07 09:34:11 +01:00
python-jose==2.0.2 # via moto
requirements: Upgrade django-auth-ldap to 1.6.0. The autenticate function now follows the signature of Django 2.0 https://github.com/django-auth-ldap/ django-auth-ldap/commit/27a8052b26f1d3a43cdbcdfc8e7dc0322580adae Also AUTH_LDAP_CACHE_GROUPS is depricated in favor of AUTH_LDAP_CACHE_TIMEOUT.
2018-08-01 12:38:41 +02:00
python-ldap==3.1.0 # via django-auth-ldap, pyldap
requirements: Upgrade python-twitter to 3.5.
2018-11-09 16:13:21 +01:00
python-twitter==3.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
python3-openid==3.1.0 # via social-auth-core
requirements: Upgrade pytz from 2018.5 to 2018.9.
2019-01-07 12:06:23 +01:00
pytz==2018.9
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
pyyaml==3.13 # via pyaml, yamole
qrcode==6.0 # via django-two-factor-auth
queuelib==1.5.0 # via scrapy
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
recommonmark==0.4.0
redis==2.10.6
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
regex==2018.11.22
requirements: Upgrade a few dependencies.
2018-11-07 01:23:13 +01:00
requests-oauthlib==1.0.0
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
requests[security]==2.21.0 # via aws-xray-sdk, docker, matrix-client, moto, premailer, pyoembed, python-digitalocean, python-gcm, python-twitter, requests-oauthlib, responses, social-auth-core, sphinx, stripe, twilio
responses==0.10.5 # via moto
requirements: Upgrade rsa to 4.0.
2018-11-09 16:16:11 +01:00
rsa==4.0
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
s3transfer==0.1.13 # via boto3
requirements: Upgrade Scrapy to 1.5.1.
2018-07-30 14:11:01 +02:00
scrapy==1.5.1
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
service-identity==18.1.0 # via scrapy
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
sh==1.11 # via gitlint
simplegeneric==0.8.1 # via ipython
requirements: Upgrade six from 1.11.0 to 1.12.0.
2019-01-07 16:32:53 +01:00
six==1.12.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
smmap==0.9.0
requirements: Upgrade snakeviz to 1.0.0.
2018-11-09 16:17:22 +01:00
snakeviz==1.0.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
snowballstemmer==1.2.1
requirements: Upgrade social-auth-app-django to 3.1.0.
2018-11-09 16:18:35 +01:00
social-auth-app-django==3.1.0
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
social-auth-core==2.0.0 # via social-auth-app-django
requirements: Upgrade sockjs-tornado to 1.0.6.
2018-11-09 16:19:45 +01:00
sockjs-tornado==1.0.6
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
soupsieve==1.6.2 # via beautifulsoup4
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
sourcemap==0.2.1
requirements: Upgrade sphinx-rtd-theme to 0.4.2.
2018-11-12 07:48:44 +01:00
sphinx-rtd-theme==0.4.2
requirements: Upgrade Sphinx to 1.8.3.
2019-01-07 18:24:47 +01:00
sphinx==1.8.3
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
sphinxcontrib-websupport==1.1.0 # via sphinx
requirements: Upgrade SQLAlchemy from 1.2.14 to 1.2.15.
2019-01-07 16:37:28 +01:00
sqlalchemy==1.2.15
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
statsd==3.3.0 # via django-statsd-mozilla
requirements: Upgrade stripe from 2.16.0 to 2.17.0.
2019-01-07 16:40:35 +01:00
stripe==2.17.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
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 from 6.19.2 to 6.22.1.
2019-01-07 16:44:10 +01:00
twilio==6.22.1
requirements: Upgrade Twisted to 18.9.0.
2018-11-12 07:55:13 +01:00
twisted==18.9.0
requirements: Upgrade beautifulsoup4 from 4.6.3 to 4.7.1.
2019-01-07 08:50:53 +01:00
typed-ast==1.1.1 # via mypy
requirements: Upgrade typing to 3.6.6.
2018-11-12 07:57:00 +01:00
typing==3.6.6
dependencies: Upgrade mypy to version 0.641. This requires upgrading a few other packages that mypy depends on.
2018-10-19 23:06:16 +02:00
typing_extensions==3.6.6
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
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
urllib3==1.24.1 # via botocore, requests, transifex-client
requirements: Upgrade virtualenv-clone to 0.4.0.
2018-11-12 07:58:31 +01:00
virtualenv-clone==0.4.0
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
w3lib==1.19.0 # via parsel, scrapy
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
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
websocket-client==0.54.0 # via docker
werkzeug==0.14.1 # via moto
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
wrapt==1.10.11 # via aws-xray-sdk
xmltodict==0.11.0 # via moto
requirements: Upgrade yamole from 2.1.5 to 2.1.6.
2019-01-07 16:47:23 +01:00
yamole==2.1.6
requirements: Update recursive dependencies. This was generated by: * `rm -f requirements/*.txt` * `./tools/update-locked-requirements` and passes tests. The effect is to unpin ourselves from old versions of a bunch of recursive dependencies of our third-party dependencies.
2018-11-13 21:29:10 +01:00
zope.interface==4.6.0 # via twisted