darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-09-09 17:45:32 -04:00
Code Issues Packages Projects Releases Wiki Activity

Don’t put version number in requirements twice

Browse Source 
It’s a pain having to remember to update both of them. Looks like `pip`
now supports a different syntax without the `egg` bit which means a git
dependency only needs the version number changing in one place.
This commit is contained in:
Chris Hill-Scott
2021-11-23 11:27:12 +00:00
parent ded7fa524f
commit 1aa79eb9a6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
requirements.in
View File

@@ -30,8 +30,8 @@ pyproj==3.2.1
awscli-cwlogs>=1.4,<1.5 awscli-cwlogs>=1.4,<1.5
itsdangerous==1.1.0 # pyup: <2 itsdangerous==1.1.0 # pyup: <2
git+https://github.com/alphagov/notifications-utils.git@48.0.0#egg=notifications-utils==48.0.0 notifications-utils @ git+https://github.com/alphagov/notifications-utils.git@48.0.0
git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.8-alpha#egg=govuk-frontend-jinja==0.5.8-alpha govuk-frontend-jinja @ git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.8-alpha
# cryptography 3.4+ incorporates Rust code, which isn't supported on PaaS # cryptography 3.4+ incorporates Rust code, which isn't supported on PaaS
# e.g. https://github.com/alphagov/notifications-api/pull/3126 # e.g. https://github.com/alphagov/notifications-api/pull/3126