Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/tools/update-locked-requirements

21 lines
864 B
Plaintext
Raw Normal View History

Lock the recursive requirements in common.txt via pip-compile. The commit is composed of: (1) distill out top-level dependencies in common.txt, (2) add -e flag to the vcs-based packages because pip-compile can't do without, (3) pip-compile/generate the locked files then remove the -e flags from the lockfile, (4) pin pathlib2 to dev.txt because it turns out it is a direct requirement of documentation_crawler, (5) document the structure and add an automation script (6) remove cryptography==1.9 from requirements/scrapy.txt since cryptography is automatically added from pyopenssl (7) add sed command to remove future/futures from the generated lock file in python3 (this should have been automatically handled by pip-compile, so pending for the feature from pip-compile) Tweaked by tabbott to update PROVISION_VERSION and add a missing `first` dependency.
2017-05-12 02:30:38 +02:00
#!/usr/bin/env bash
set -e
deps: Organize tools/update-locked-requirements a bit further. A couple of remarks still reflected the Python 2 world; and the "Remove the editable flag" comment was confusingly above a line that it looks like it could be talking about, but isn't.
2017-09-15 00:45:08 +02:00
# Make sure the Zulip dev virtualenv exists, and operate within it.
Lock the recursive requirements in common.txt via pip-compile. The commit is composed of: (1) distill out top-level dependencies in common.txt, (2) add -e flag to the vcs-based packages because pip-compile can't do without, (3) pip-compile/generate the locked files then remove the -e flags from the lockfile, (4) pin pathlib2 to dev.txt because it turns out it is a direct requirement of documentation_crawler, (5) document the structure and add an automation script (6) remove cryptography==1.9 from requirements/scrapy.txt since cryptography is automatically added from pyopenssl (7) add sed command to remove future/futures from the generated lock file in python3 (this should have been automatically handled by pip-compile, so pending for the feature from pip-compile) Tweaked by tabbott to update PROVISION_VERSION and add a missing `first` dependency.
2017-05-12 02:30:38 +02:00
if [ ! -d /srv/zulip-py3-venv ]; then
./tools/setup/setup_venvs.py
fi
deps: Organize tools/update-locked-requirements a bit further. A couple of remarks still reflected the Python 2 world; and the "Remove the editable flag" comment was confusingly above a line that it looks like it could be talking about, but isn't.
2017-09-15 00:45:08 +02:00
source /srv/zulip-py3-venv/bin/activate
Lock the recursive requirements in common.txt via pip-compile. The commit is composed of: (1) distill out top-level dependencies in common.txt, (2) add -e flag to the vcs-based packages because pip-compile can't do without, (3) pip-compile/generate the locked files then remove the -e flags from the lockfile, (4) pin pathlib2 to dev.txt because it turns out it is a direct requirement of documentation_crawler, (5) document the structure and add an automation script (6) remove cryptography==1.9 from requirements/scrapy.txt since cryptography is automatically added from pyopenssl (7) add sed command to remove future/futures from the generated lock file in python3 (this should have been automatically handled by pip-compile, so pending for the feature from pip-compile) Tweaked by tabbott to update PROVISION_VERSION and add a missing `first` dependency.
2017-05-12 02:30:38 +02:00
requirements: Lock prod.txt instead of its py3_common dependency. `py3_common.txt` is no longer locked.
2017-08-22 06:26:59 +02:00
pip-compile --output-file requirements/prod_lock.txt requirements/prod.txt
Lock the recursive requirements in dev.txt via pip-compile. First, all the lines of py3_dev.txt except for mypy.txt are mv-ed to dev.txt. Then dev_lock.txt is generated from dev.txt to be used by py3_dev.txt. `click` is removed from moto.txt since it is already a dependency of several libraries and will appear as an autogenerated dependency.
2017-08-22 02:26:16 +02:00
pip-compile --output-file requirements/dev_lock.txt requirements/dev.txt
deps: Organize tools/update-locked-requirements a bit further. A couple of remarks still reflected the Python 2 world; and the "Remove the editable flag" comment was confusingly above a line that it looks like it could be talking about, but isn't.
2017-09-15 00:45:08 +02:00
deps: Explain the `-e` oddness, and handle it uniformly.
2017-09-15 00:45:26 +02:00
# Remove the editable flag in the lock files. It's there because pip-compile
# can't yet do without it (see https://github.com/jazzband/pip-tools/issues/272
# upstream), but in the output of pip-compile it's no longer needed.
deps: Organize tools/update-locked-requirements a bit further. A couple of remarks still reflected the Python 2 world; and the "Remove the editable flag" comment was confusingly above a line that it looks like it could be talking about, but isn't.
2017-09-15 00:45:08 +02:00
sed -i 's/-e //' requirements/prod_lock.txt requirements/dev_lock.txt
Lock the recursive requirements in common.txt via pip-compile. The commit is composed of: (1) distill out top-level dependencies in common.txt, (2) add -e flag to the vcs-based packages because pip-compile can't do without, (3) pip-compile/generate the locked files then remove the -e flags from the lockfile, (4) pin pathlib2 to dev.txt because it turns out it is a direct requirement of documentation_crawler, (5) document the structure and add an automation script (6) remove cryptography==1.9 from requirements/scrapy.txt since cryptography is automatically added from pyopenssl (7) add sed command to remove future/futures from the generated lock file in python3 (this should have been automatically handled by pip-compile, so pending for the feature from pip-compile) Tweaked by tabbott to update PROVISION_VERSION and add a missing `first` dependency.
2017-05-12 02:30:38 +02:00
# pip-tools bug; future, futures are obsolete in python3
deps: Simplify tools/update-locked-requirements slightly. This makes the code a little more concise and also more uniform, treating `future` the same in prod and in dev. The non-uniformity looks like an oversight in 2be8a793e, one of the commits that updated this code for the Python 3-only world.
2017-09-15 00:56:33 +02:00
sed -i '/futures==/d' requirements/prod_lock.txt requirements/dev_lock.txt
sed -i '/future==/d' requirements/prod_lock.txt requirements/dev_lock.txt