zulip/requirements
Alex Vandiver 50a2a54393 test_invite: Rework and expand invitation limit tests.
This adds tests for more corner cases, in exchange for dropping the
query count tests, which were of dubious utility.  It also adds the
time-machine library to mock the current time to test that the limits
do expire.
2023-03-16 11:41:49 -07:00
..
README.md requirements: Remove unused mypy.txt lock file. 2022-09-08 11:08:06 -07:00
common.in requirements: Upgrade Python requirements. 2023-03-05 14:46:28 -08:00
dev.in test_invite: Rework and expand invitation limit tests. 2023-03-16 11:41:49 -07:00
dev.txt test_invite: Rework and expand invitation limit tests. 2023-03-16 11:41:49 -07:00
docs.in requirements: Upgrade Python requirements. 2023-03-05 14:46:28 -08:00
docs.txt requirements: Upgrade Python requirements. 2023-03-05 14:46:28 -08:00
mypy.in requirements: Upgrade Python requirements. 2022-11-03 14:08:58 -07:00
pip.in requirements: Upgrade Python requirements. 2021-05-07 22:42:39 -07:00
pip.txt requirements: Upgrade Python requirements. 2023-03-05 14:46:28 -08:00
prod.in requirements: Remove unnecessary version bounds from *.in. 2019-09-23 13:23:58 -07:00
prod.txt requirements: Upgrade Python requirements. 2023-03-05 14:46:28 -08:00

README.md

The dependency graph of the requirements is as follows:

dev +-> prod +-> common
+
|
v
docs,pip

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

Steps to update a lock file, e.g. to update ipython from 5.3.0 to latest version:

  1. Remove entry for ipython==5.3.0 in dev.txt.
  2. Run ./tools/update-locked-requirements, which will generate new entries, pinned to the latest version.
  3. Increase PROVISION_VERSION in version.py.
  4. Run ./tools/provision to install the new deps and test them.
  5. Commit your changes.