requirements-app.txt

# Run `make freeze-requirements` to update requirements.txt
# with package version changes made in requirements-app.txt

ago==0.0.93
govuk-bank-holidays==0.8
humanize==2.5.0
Flask==1.1.2
Flask-WTF==0.14.3
Flask-Login==0.5.0

blinker==1.4
pyexcel==0.6.2
pyexcel-io==0.5.20
pyexcel-xls==0.5.8
pyexcel-xlsx==0.5.8
pyexcel-ods3==0.5.3
pytz==2020.1
gunicorn==20.0.4
eventlet==0.25.2
notifications-python-client==5.6.0

# PaaS
awscli-cwlogs>=1.4,<1.5
itsdangerous==1.1.0

git+https://github.com/alphagov/notifications-utils.git@40.3.1#egg=notifications-utils==40.3.1
git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.1-alpha#egg=govuk-frontend-jinja==0.5.1-alpha

# gds-metrics requires prometheseus 0.2.0, override that requirement as later versions bring significant performance gains
prometheus-client==0.8.0
gds-metrics==0.2.0
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00			# Run `make freeze-requirements` to update requirements.txt
			`# with package version changes made in requirements-app.txt`

Update ago from 0.0.92 to 0.0.93 2018-10-06 20:15:33 +01:00			`ago==0.0.93`
Update govuk-bank-holidays from 0.6 to 0.8 2020-06-15 14:50:02 +01:00			`govuk-bank-holidays==0.8`
Update humanize from 2.4.1 to 2.5.0 2020-07-06 14:52:02 +01:00			`humanize==2.5.0`
Update flask from 1.1.1 to 1.1.2 2020-04-27 14:49:06 +01:00			`Flask==1.1.2`
Update flask-wtf from 0.14.2 to 0.14.3 2020-02-10 13:47:05 +00:00			`Flask-WTF==0.14.3`
upgrade flask_login to 0.5.0 flask_login sets a bunch of variables in the session object. We only use one of them, `user_id`. We set that to the user id from the database, and refer to it all over the place. However, in flask_login 0.5.0 they prefix this with an underscore to prevent people accidentally overwriting it etc. So when a user logs in we need to make sure that we set user_id manually so we can still use it. flask_login sets a bunch of variables on the `flask.session` object. However, this session object isn't the one that gets passed in to the request context by flask - that one can only be modified outside of requests from within the session_transaction context manager (see [1]). So, flask_login populates the normal session and then we need to copy all of those values across. We didn't need to do this previously because we already set the `user_id` value on line 20 of tests/__init__.py, but now that flask_login is looking for `_user_id` instead we need to do this properly. [1] https://flask.palletsprojects.com/en/1.1.x/testing/#accessing-and-modifying-sessions 2020-03-06 15:41:13 +00:00			`Flask-Login==0.5.0`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00
			`blinker==1.4`
Update pyexcel from 0.6.1 to 0.6.2 2020-06-15 14:50:03 +01:00			`pyexcel==0.6.2`
Update pyexcel-io from 0.5.18 to 0.5.20 2019-08-26 14:43:09 +01:00			`pyexcel-io==0.5.20`
Update pyexcel-xls from 0.5.7 to 0.5.8 2018-09-03 09:56:45 +01:00			`pyexcel-xls==0.5.8`
bump requirements 2020-01-21 14:21:48 +00:00			`pyexcel-xlsx==0.5.8`
Update pyexcel-ods3 from 0.5.2 to 0.5.3 2018-11-27 08:03:16 +00:00			`pyexcel-ods3==0.5.3`
Update pytz from 2019.3 to 2020.1 2020-05-04 14:49:07 +01:00			`pytz==2020.1`
bump reqs 2020-02-04 17:16:58 +00:00			`gunicorn==20.0.4`
Update eventlet from 0.25.1 to 0.25.2 2020-04-27 14:49:09 +01:00			`eventlet==0.25.2`
Update notifications-python-client from 5.5.1 to 5.6.0 2020-05-25 14:49:03 +01:00			`notifications-python-client==5.6.0`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00
			`# PaaS`
			`awscli-cwlogs>=1.4,<1.5`
Upgrade itsdangerous Version 1.1.0 has reverted the breaking change (moving from sha1 to sha256) that was introduced in version 1.0.0. Upgrading now so that we can take advantage of this bug fix: https://github.com/pallets/itsdangerous/issues/46 2020-02-19 13:47:35 +00:00			`itsdangerous==1.1.0`
Update notifications-utils to 30.5.6 This brings in the change to email validation which removes obscure white space from email addresses. 2018-10-29 10:21:04 +00:00
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session 2020-07-06 10:53:14 +01:00			`git+https://github.com/alphagov/notifications-utils.git@40.3.1#egg=notifications-utils==40.3.1`
bump requirements 2020-01-21 14:21:48 +00:00			`git+https://github.com/alphagov/govuk-frontend-jinja.git@v0.5.1-alpha#egg=govuk-frontend-jinja==0.5.1-alpha`
Revert "Revert "Statsd to prometheus"" 2020-07-01 13:27:12 +01:00
			`# gds-metrics requires prometheseus 0.2.0, override that requirement as later versions bring significant performance gains`
			`prometheus-client==0.8.0`
			`gds-metrics==0.2.0`