zulip/requirements
Eeshan Garg c45517f544 python-zulip-api: Upgrade to PyPI package release 0.3.8.
There's one migration required by this release:

* queue_processors: Stop passing state_handler to handle_message.

  state_handler is now a property of bot_handler and thus, does
  not need to be passed to bot_handler.handle_message().

  The commit responsible is:
  2a74ad11c5
2017-11-27 20:31:37 -08:00
..
README.md requirements: Rename requirements files. 2017-11-21 02:38:26 +05:30
common.in python-zulip-api: Upgrade to PyPI package release 0.3.8. 2017-11-27 20:31:37 -08:00
dev.in requirements: Rename requirements files. 2017-11-21 02:38:26 +05:30
dev.txt python-zulip-api: Upgrade to PyPI package release 0.3.8. 2017-11-27 20:31:37 -08:00
docs.in requirements: Add back explicit typing dependencies. 2017-11-20 13:47:16 -08:00
docs.txt requirements: Add back explicit typing dependencies. 2017-11-20 13:47:16 -08:00
mypy.in requirements: Upgrade mypy to 0.550. 2017-11-25 10:06:27 -08:00
mypy.txt requirements: Upgrade mypy to 0.550. 2017-11-25 10:06:27 -08:00
pip.txt Fix various typos. 2017-11-09 16:26:38 +01:00
prod.in requirements: Rename requirements files. 2017-11-21 02:38:26 +05:30
prod.txt python-zulip-api: Upgrade to PyPI package release 0.3.8. 2017-11-27 20:31:37 -08:00
thumbor.in requirements: Rename requirements files. 2017-11-21 02:38:26 +05:30
thumbor.txt requirements: Rename requirements files. 2017-11-21 02:38:26 +05:30

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.