.pyup.yml

# see https://pyup.io/docs/configuration/ for all available options

schedule: "every week on monday"

search: False
requirements:
  - requirements.in
  - requirements_for_test.txt
Update pyup to run once a week. 2019-03-25 11:14:05 +00:00			`# see https://pyup.io/docs/configuration/ for all available options`

			`schedule: "every week on monday"`

			`search: False`
			`requirements:`
Tell PyUp to look at `.in` files We only want PyUp to be checking for the dependencies we specify directly, not any sub-dependencies. By telling it to now look only at `.in` files we preserve this existing behaviour. 2020-12-29 13:33:42 +00:00			`- requirements.in`
Stop locking non-test dependencies twice Currently we have a situation where we're not running tests against new versions of dependencies, as requirements_for_test.txt is not being kept in-sync with requirements.txt by pyup. Deploys are only working because Concourse silently ignores version issues. From a deployment log: awscli 1.18.211 has requirement PyYAML<5.4,>=3.10; python_version != "3.4", but you'll have pyyaml 5.4 which is incompatible. This switches to a single requirements file for test dependencies, in order to keep it in-sync with requirements.txt i.e. we run our tests against the same versions of dependencies that we deploy with, and the build fails if we try to use package versions that are not mutually compatible, as this example PR shows [1]. ERROR: Cannot install -r requirements_for_test.txt (line 17), -r requirements_for_test.txt (line 198) and pyyaml==5.4.1 because these package versions have conflicting dependencies. We shouldn't need to have fine-grained locking on test dependencies, beyond those we want to list manually in the file. [1]: https://github.com/alphagov/notifications-admin/pull/3804 2021-02-16 17:08:03 +00:00			`- requirements_for_test.txt`