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

192 lines
6.1 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
pypi: Upgrade to release 0.5.5.
2018-09-26 03:21:35 +02:00
git+https://github.com/zulip/python-zulip-api.git@0.5.5#egg=zulip==0.5.5_git&subdirectory=zulip
git+https://github.com/zulip/python-zulip-api.git@0.5.5#egg=zulip_bots==0.5.5+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
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: 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 to 4.6.3.
2018-11-09 07:46:19 +01:00
beautifulsoup4==4.6.3
requirements: Upgrade moto to 1.3.3.
2018-05-02 18:30:30 +02:00
boto3==1.7.11 # 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 moto to 1.3.3.
2018-05-02 18:30:30 +02:00
botocore==1.10.11 # via boto3, moto, s3transfer
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
cachetools==2.1.0 # via google-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
cchardet==2.1.1
requirements: Upgrade certifi to 2018.10.15.
2018-11-09 07:48:14 +01:00
certifi==2018.10.15
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 moto to 1.3.3.
2018-05-02 18:30:30 +02:00
cookies==2.2.1 # via moto, responses
requirements: Upgrade cryptography to 2.1.4.
2018-02-13 19:51:53 +01:00
coverage==4.5.1
requirements: Upgrade a few dependencies.
2018-11-07 01:23:13 +01:00
cryptography==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
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
requirements: Upgrade disposable-email-domains to 0.0.37.
2018-11-09 07:51:02 +01:00
disposable-email-domains==0.0.37
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
django-auth-ldap==1.6.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
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
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: Update Django to 1.11.16.
2018-10-31 20:12:11 +01:00
django==1.11.16
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
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.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
google-auth==1.5.0 # 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 to 0.11.3.
2018-04-01 15:08:04 +02:00
httplib2==0.11.3
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
hyperlink==17.3.1 # via twisted
idna==2.6 # via cryptography, requests
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: 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.2.5.
2018-10-31 20:08:53 +01:00
lxml==4.2.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
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 to 1.3.3.
2018-05-02 18:30:30 +02:00
moto==1.3.3
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
mypy==0.641
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: 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: 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.3.0.
2018-11-09 11:26:42 +01:00
pillow==5.3.0
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.5. Bunch of bug fixes. * Allow non-ascii chars in namedtuple fields (regression introduced fixing ticket #211). * Fixed adaptation of arrays of arrays of nulls (ticket #325). * Fixed building on Solaris 11 and derivatives such as SmartOS and illumos (ticket #677). * Maybe fixed building on MSYS2 (as reported in ticket #658). * Allow string subclasses in connection and other places (ticket #679). * Don’t raise an exception closing an unused named cursor (ticket #716). * Wheel package compiled against PostgreSQL 10.4 libpq and OpenSSL 1.0.2o.
2018-07-30 13:11:09 +02:00
psycopg2==2.7.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
ptyprocess==0.5.2 # 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: 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
pyaml==17.10.0 # via moto
requirements: Upgrade pyasn1-modules to 0.2.2. rfc2986 module added and some documentation changes.
2018-07-30 13:30:08 +02:00
pyasn1-modules==0.2.2
requirements: Upgrade pyasn1 to 0.4.4. Two minor bug fixes.
2018-07-30 13:23:42 +02:00
pyasn1==0.4.4
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: 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
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: 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
requirements: Upgrade PyJWT to 1.6.4.
2018-05-24 21:47:19 +02:00
pyjwt==1.6.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
pyldap==3.0.0.post1 # via fakeldap
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
requirements: Upgrade a few dependencies.
2018-11-07 01:23:13 +01:00
pyopenssl==18.0.0 # via ndg-httpsclient, requests, 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.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 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 to 2018.5. https://github.com/stub42/pytz/blob/master/tz/NEWS
2018-07-30 14:50:39 +02:00
pytz==2018.5
requirements: Add dependency for parsing OpenAPI-formatted YAML files.
2018-05-26 00:59:35 +02:00
pyyaml==3.12 # via pyaml, 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
queuelib==1.4.2 # via scrapy
recommonmark==0.4.0
redis==2.10.6
regex==2017.11.9
requirements: Upgrade a few dependencies.
2018-11-07 01:23:13 +01:00
requests-oauthlib==1.0.0
requests[security]==2.20.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
requirements: Upgrade moto to 1.3.3.
2018-05-02 18:30:30 +02:00
responses==0.9.0 # via moto
requirements: Upgrade rsa to 4.0.
2018-11-09 16:16:11 +01:00
rsa==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
s3transfer==0.1.11 # via boto3
requirements: Upgrade Scrapy to 1.5.1.
2018-07-30 14:11:01 +02:00
scrapy==1.5.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
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
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
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 sphinx-rtd-theme to 0.4.1.
2018-07-30 14:20:29 +02:00
sphinx-rtd-theme==0.4.1
requirements: Upgrade Sphinx to 1.7.6.
2018-07-30 14:16:28 +02:00
sphinx==1.7.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
sphinxcontrib-websupport==1.0.1 # via sphinx
requirements: Upgrade SQLAlchemy to 1.2.10. Bunch of bug fixes. http://docs.sqlalchemy.org/en/latest/changelog/ changelog_12.html#change-1.2.10
2018-07-30 14:33:35 +02:00
sqlalchemy==1.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
statsd==3.2.1 # via django-statsd-mozilla
requirements: Upgrade stripe to 2.3.0.
2018-07-31 17:56:59 +02:00
stripe==2.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
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 a few dependencies.
2018-11-07 01:23:13 +01:00
twilio==6.19.2
requirements: Upgrade Twisted to 18.4.0.
2018-05-02 19:59:38 +02:00
twisted==18.4.0
requirements: Upgrade mypy to 0.620. Fixes #9975.
2018-07-28 21:02:49 +02:00
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
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
urllib3==1.22 # via requests, transifex-client
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
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
requirements: Upgrade yamole to 2.1.5.
2018-06-21 00:37:50 +02:00
yamole==2.1.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
zope.interface==4.4.3 # via twisted