zulip/requirements/mypy.txt

#
# 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 .
#
mypy==0.540
typed-ast==1.1.0          # via mypy
typing==3.6.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			`#`
			`# 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: Update mypy to latest version. This involves fixing the mypy annotations in one file 2017-10-28 01:57:22 +02:00			`mypy==0.540`
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			`typed-ast==1.1.0 # via mypy`
requirements: Add back explicit typing dependencies. These are needed to make the output the same on Trusty and Xenial. 2017-11-20 22:45:49 +01:00			`typing==3.6.2`