zulip/requirements
Eeshan Garg a6abafa54b python-zulip-api: Upgrade to release 0.6.0. 2019-03-19 20:07:53 -02:30
..
README.md requirements: Improve README's format. 2018-05-26 06:26:14 -07:00
common.in python-zulip-api: Upgrade to release 0.6.0. 2019-03-19 20:07:53 -02:30
dev.in requirements: Upgrade isort from 4.3.10 to 4.3.11. 2019-03-06 09:31:24 -08:00
dev.txt python-zulip-api: Upgrade to release 0.6.0. 2019-03-19 20:07:53 -02:30
docs.in Revert "docs: Update dependencies for docs." 2019-03-06 09:55:51 -08:00
docs.txt Revert "docs: Update dependencies for docs." 2019-03-06 09:55:51 -08:00
mypy.in dependencies: Upgrade mypy to version 0.650. 2018-12-09 22:20:12 -08:00
mypy.txt dependencies: Upgrade mypy to version 0.650. 2018-12-09 22:20:12 -08:00
pip.txt requirements: Upgrade wheel from 0.32.3 to 0.33.1. 2019-03-06 09:31:24 -08:00
prod.in requirements: Upgrade uWSGI to 2.0.17.1. 2018-07-31 11:13:22 -07:00
prod.txt python-zulip-api: Upgrade to release 0.6.0. 2019-03-19 20:07:53 -02:30
thumbor.in thumbor requirements: Upgrade virtualenv-clone from 0.4.0 to 0.5.1. 2019-01-30 09:50:43 -08:00
thumbor.txt thumbor requirements: Upgrade virtualenv-clone from 0.4.0 to 0.5.1. 2019-01-30 09:50:43 -08:00
unupgradable.json requirements: Fix JSON syntax in unupgradables.json. 2019-01-30 07:30:31 +00:00

README.md

The dependency graph of the requirements is as follows:

dev         prod
+ +          +
| +->common<-+
v
mypy,docs

Of the files, only dev, prod, and mypy have been used in the install scripts directly. The rest are implicit dependencies.

common and dev are locked.

Steps to update a lock file, e.g. to update ipython from 5.3.0 to 6.0.0 in common.in and propagate it to dev.txt and prod.txt: 0. Replace ipython==5.4.1 with ipython==6.0.0 in common.in.

  1. Run ./tools/update-locked-requirements.
  2. Increase PROVISION_VERSION in version.py.
  3. Run ./tools/provision to install the new deps and test them.
  4. Commit your changes.