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

33 lines
919 B
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 albaster to 0.7.12.
2018-11-09 07:31:21 +01:00
alabaster==0.7.12
requirements: Upgrade Babel to 2.5.3.
2018-02-13 19:26:25 +01:00
babel==2.5.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
certifi==2018.10.15 # via 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
chardet==3.0.4 # via requests
commonmark==0.5.4
requirements: Upgrade docutils to 0.14.
2017-08-16 21:55:52 +02:00
docutils==0.14
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
idna==2.7 # via requests
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
jinja2==2.10 # via sphinx
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
markupsafe==1.1.0 # via jinja2
packaging==18.0 # 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
pygments==2.2.0 # via sphinx
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
pytz==2018.7 # via babel
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
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
requests==2.20.1 # via sphinx
requirements: Upgrade Sphinx to 1.7.0.
2018-02-13 21:30:29 +01:00
six==1.11.0 # via packaging, sphinx
Requirements: Add comments in docs.txt.
2016-06-24 18:50:38 +02:00
snowballstemmer==1.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.2.
2018-11-12 08:56:44 +01:00
sphinx==1.8.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
sphinxcontrib-websupport==1.1.0 # via sphinx
requirements: Upgrade typing to 3.6.6.
2018-11-12 07:57:00 +01:00
typing==3.6.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
urllib3==1.24.1 # via requests