darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-02-16 00:14:18 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
203393de235631db0ce3c38dec85da170a634fba
notifications-admin/requirements.txt

79 lines
1.5 KiB
Plaintext
Raw Normal View History

Make pyup ignore requirements.txt We don't want pyup.io upgrading sub-dependencies listed in the requirements.txt file since it does it whenever a new version is available regardless of what our application dependencies require.
2018-07-30 16:43:44 +01:00
# pyup: ignore file
# This file is autogenerated. Do not edit it manually.
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
Freeze requirements
2018-10-29 16:40:29 +00:00
ago==0.0.93
Update flask from 0.12.2 to 1.0.2
2018-05-02 15:49:01 +01:00
Flask==1.0.2
Update flask-wtf from 0.11 to 0.14.2
2017-07-06 14:22:44 +01:00
Flask-WTF==0.14.2
Update flask-login from 0.4.0 to 0.4.1
2017-12-02 02:50:50 +00:00
Flask-Login==0.4.1
Add link to Bleach bugtracker Explains why we’re using forked version of Weasyprint
2016-12-20 13:43:53 +00:00
Missing requirement
2016-04-27 16:45:50 +01:00
blinker==1.4
Freeze requirements
2018-12-14 13:11:31 +00:00
pyexcel==0.5.10
Update pyexcel-io from 0.5.10 to 0.5.11
2018-12-04 07:18:25 +00:00
pyexcel-io==0.5.11
Freeze requirements
2018-09-03 10:13:51 +01:00
pyexcel-xls==0.5.8
Update pyexcel-xlsx from 0.5.5 to 0.5.6
2018-03-26 23:41:09 +01:00
pyexcel-xlsx==0.5.6
Freeze requirements
2018-11-27 10:08:26 +00:00
pyexcel-ods3==0.5.3
Freeze requirements
2019-01-10 13:40:53 +00:00
pytz==2018.9
Stop gunicorn from terminating eventlet workers on timeout According to gunicorn `timeout` docs, async workers shouldn't be terminated after the request time exceeds the specified timeout as long as the worker process is still communicating. This makes sense for async workers since they generally don't block other requests from processing. This is the behaviour we've seen on notifications-api - requests can sometimes take much longer than the default 30 second timeout and still succeed. For the admin app however gunicorn has been shutting down workers after 30s with `[CRITICAL] WORKER TIMEOUT`. This results in a 502 response from the admin app. Most of these requests fail because the underlying requests to the api is taking longer than 30 seconds, however we haven't seen this in the logs originally since unlike the admin app, api requests succeed (even though their response is no longer needed). This seems like a bug in newer versions of gunicorn, downgrading it to the version that the api is currently using solves the problem by allowing admin requests to take longer than 30 seconds. (Tested by trying requests with a `time.sleep(30)` locally). It's not clear what exactly the bug in gunicorn is, but this also potentially unblocks eventlet workers and allows them to process more than one request at a time.
2018-09-18 11:25:42 +01:00
gunicorn==19.7.1 # >19.8 stops eventlet workers after a timeout
Update eventlet from 0.22.1 to 0.24.1
2018-08-20 11:46:28 +01:00
eventlet==0.24.1
Freeze requirements
2019-02-08 15:25:31 +00:00
notifications-python-client==5.3.0
Integrated logging from the utils repo
2016-01-07 15:39:36 +00:00
Add awslogs logging for PaaS
2017-02-14 16:17:30 +00:00
# PaaS
awscli-cwlogs>=1.4,<1.5
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
# Putting upgrade on hold due to v1.0.0 using sha512 instead of sha1 by default
itsdangerous==0.24 # pyup: <1.0.0
Display postage everywhere we display a letter To avoid the problem of having confusing defaults, the postage is now set explicitly on every template. Putting the postage ‘inside’ the letter template makes the interaction for changing it consistent with how other parts of the template are added. Plus everyone loves skeumorphism.
2018-09-10 11:21:43 +01:00
git+https://github.com/alphagov/notifications-utils.git@31.0.0#egg=notifications-utils==31.0.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
## The following requirements were added by pip freeze:
Freeze requirements
2019-02-08 15:25:31 +00:00
awscli==1.16.100
bump utils brings in redis 3
2019-01-08 15:00:42 +00:00
bleach==3.0.2
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
boto3==1.6.16
Freeze requirements
2019-02-08 15:25:31 +00:00
botocore==1.12.90
Freeze requirements
2018-12-14 13:11:31 +00:00
certifi==2018.11.29
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
chardet==3.0.4
update jobs to take into account first class
2018-09-28 17:08:28 +01:00
Click==7.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
colorama==0.3.9
Freeze requirements
2018-12-14 13:11:31 +00:00
dnspython==1.16.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
docopt==0.6.2
docutils==0.14
et-xmlfile==1.0.1
Flask-Redis==0.3.0
Post to the API when moving folders and templates This commit adds logic to: - take the list of selected folders and templates - split it into two lists (of folders and templates) - `POST` that data to the API, to effect the movement of said folders and templates I’ve tried to architect it in such a way that we can easily add more template ‘operations’ in the future, as we add more forms to the choose template page.
2018-11-08 14:46:18 +00:00
future==0.17.1
Update notifications-python-client from 5.0.1 to 5.1.0
2018-09-05 10:14:31 +01:00
greenlet==0.4.15
Freeze requirements
2018-12-14 13:11:31 +00:00
idna==2.8
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
jdcal==1.4
Jinja2==2.10
jmespath==0.9.3
bump utils brings in redis 3
2019-01-08 15:00:42 +00:00
lml==0.0.9
lxml==4.3.0
Post to the API when moving folders and templates This commit adds logic to: - take the list of selected folders and templates - split it into two lists (of folders and templates) - `POST` that data to the API, to effect the movement of said folders and templates I’ve tried to architect it in such a way that we can easily add more template ‘operations’ in the future, as we add more forms to the choose template page.
2018-11-08 14:46:18 +00:00
MarkupSafe==1.1.0
bump utils brings in redis 3
2019-01-08 15:00:42 +00:00
mistune==0.8.4
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
monotonic==1.5
Freeze requirements
2019-02-08 15:25:31 +00:00
openpyxl==2.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
orderedset==2.0.1
bump utils brings in redis 3
2019-01-08 15:00:42 +00:00
phonenumbers==8.10.2
Freeze requirements
2019-01-02 10:27:10 +00:00
pyasn1==0.4.5
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
pyexcel-ezodf==0.3.4
Freeze requirements
2018-12-14 13:11:31 +00:00
PyJWT==1.7.1
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
PyPDF2==1.26.0
Display postage everywhere we display a letter To avoid the problem of having confusing defaults, the postage is now set explicitly on every template. Putting the postage ‘inside’ the letter template makes the interaction for changing it consistent with how other parts of the template are added. Plus everyone loves skeumorphism.
2018-09-10 11:21:43 +01:00
python-dateutil==2.8.0
bump utils brings in redis 3
2019-01-08 15:00:42 +00:00
python-json-logger==0.1.10
bump reqs
2018-11-13 10:49:35 +00:00
PyYAML==3.12
Bump utils to 30.7.5 Brings in: - [x] https://github.com/alphagov/notifications-utils/pull/572
2019-02-01 09:37:02 +00:00
redis==3.1.0
Freeze requirements
2018-12-14 13:11:31 +00:00
requests==2.21.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
rsa==3.4.2
Freeze requirements
2019-02-08 15:25:31 +00:00
s3transfer==0.2.0
Freeze requirements
2018-12-14 13:11:31 +00:00
six==1.12.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
smartypants==2.0.1
bump utils brings in redis 3
2019-01-08 15:00:42 +00:00
statsd==3.3.0
Bump utils to 30.7.5 Brings in: - [x] https://github.com/alphagov/notifications-utils/pull/572
2019-02-01 09:37:02 +00:00
texttable==1.6.0
Post to the API when moving folders and templates This commit adds logic to: - take the list of selected folders and templates - split it into two lists (of folders and templates) - `POST` that data to the API, to effect the movement of said folders and templates I’ve tried to architect it in such a way that we can easily add more template ‘operations’ in the future, as we add more forms to the choose template page.
2018-11-08 14:46:18 +00:00
urllib3==1.24.1
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
webencodings==0.5.1
Werkzeug==0.14.1
Bump utils to 29.3.4 https://github.com/alphagov/notifications-utils/compare/29.3.2...bullet-for-bullet
2018-07-30 15:19:46 +01:00
WTForms==2.2.1
Remove WhiteNoise We’re now serving assets from S3 when running on PaaS. So we’ll set the appropriate caching headers there or in Cloudfront. This means that the app no longer needs to serve cache headers, which is what we were using WhiteNoise for. This commits removes WhiteNoise in favour of letting Flask handle the serving of static assets.
2018-12-21 10:40:00 +00:00
xlrd==1.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
xlwt==1.3.0
Reference in New Issue Copy Permalink