2018-07-30 16:22:20 +01:00
|
|
|
# pyup: ignore file
|
Pin all application 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.
This is based on alphagov/digitalmarketplace-api#615, so rationale
from that PR applies here.
We had a problem with unpinned packages on new deployments leading
to failed tests (e.g. alphagov/notifications-admin#2144) which is
why we're implementing this now.
After re-evaluating pipenv again, this still seems like the least
disruptive approach:
* pyup.io has experimental support for Pipfile, but doesn't respect
version ranges or updating hashes in the lock file
* CloudFoundry buildpack recognizes and supports Pipfiles out of the
box, but the support is relatively new. For example until recently
CF would install dev packages during deployment. It's also based on
generating a requirements file from the Pipfile, which doesn't
properly support pinning VCS dependencies (eg it doesn't set the
#egg= version, meaning pip will not upgrade the package if it's
already installed).
* pipenv has a strict dependency resolution algorithm, which doesn't
appear to be well documented and can cause some unexpected failures.
For example, pipenv doesn't seem to be able to install `awscli-cwlogs`
package at all, believing it to have a version conflict for `botocore`
(which it doesn't list as a direct dependency) while neither `pip` nor
`pip-tools` highlight any issues with it.
* While trying out `pipenv install` on our list of dependencies it would
regularly fail to install utils with a "Will try again." message.
While the installation succeeds after a retry, this doesn't inspire
confidence.
* The switch to Pipfile and pipenv-managed virtualenvs requires a series
of changes to `make` targets and scripts - replacing `pip install` with
`pipenv`, removing references to requirements files and prefixing
commands with `pipenv run`. While it's likely to simplify the overall
process of managing dependencies, it would require time to properly
implement across our applications and environments (Jenkins, PaaS,
docker containers, and dev machines).
2018-07-10 14:50:30 +01:00
|
|
|
# This file is autogenerated. Do not edit it manually.
|
|
|
|
|
# Run `make freeze-requirements` to update requirements.txt
|
|
|
|
|
# with package version changes made in requirements-app.txt
|
|
|
|
|
|
2020-12-14 11:40:07 +00:00
|
|
|
cffi==1.14.4
|
2020-02-12 15:30:02 +00:00
|
|
|
celery[sqs]==3.1.26.post2 # pyup: <4
|
2017-08-18 15:39:39 +01:00
|
|
|
docopt==0.6.2
|
2017-09-11 15:47:10 +01:00
|
|
|
Flask-Bcrypt==0.7.1
|
2020-12-14 11:40:07 +00:00
|
|
|
flask-marshmallow==0.14.0
|
2020-05-22 10:29:16 +01:00
|
|
|
Flask-Migrate==2.5.3
|
2019-01-07 17:12:00 +00:00
|
|
|
git+https://github.com/mitsuhiko/flask-sqlalchemy.git@500e732dd1b975a56ab06a46bd1a20a21e682262#egg=Flask-SQLAlchemy==2.3.2.dev20190108
|
2020-05-22 10:31:15 +01:00
|
|
|
Flask==1.1.2
|
2017-11-28 11:10:19 +00:00
|
|
|
click-datetime==0.2
|
2020-12-23 13:32:21 +00:00
|
|
|
eventlet==0.30.0
|
2019-11-28 18:00:46 +00:00
|
|
|
gunicorn==20.0.4
|
2020-11-06 10:56:52 +00:00
|
|
|
iso8601==0.1.13
|
2020-02-11 14:24:13 +00:00
|
|
|
itsdangerous==1.1.0
|
2020-02-05 13:00:05 +00:00
|
|
|
jsonschema==3.2.0
|
2020-12-14 11:40:07 +00:00
|
|
|
marshmallow-sqlalchemy==0.23.1 # pyup: <0.24.1 # marshmallow v3 throws errors
|
2020-05-22 10:38:27 +01:00
|
|
|
marshmallow==2.21.0 # pyup: <3 # v3 throws errors
|
2020-11-06 10:56:52 +00:00
|
|
|
psycopg2-binary==2.8.6
|
2020-12-23 13:32:21 +00:00
|
|
|
PyJWT==2.0.0
|
|
|
|
|
SQLAlchemy==1.3.22
|
2020-07-09 12:59:09 +01:00
|
|
|
strict-rfc3339==0.7
|
|
|
|
|
rfc3987==1.3.8
|
2020-12-23 13:32:21 +00:00
|
|
|
cachetools==4.2.0
|
2021-01-18 10:01:45 +00:00
|
|
|
beautifulsoup4==4.9.3
|
2021-01-18 10:01:47 +00:00
|
|
|
lxml==4.6.2
|
2015-12-14 12:58:49 +00:00
|
|
|
|
2020-12-31 12:47:03 +00:00
|
|
|
notifications-python-client==5.7.1
|
2016-04-14 18:12:33 +01:00
|
|
|
|
2017-02-13 18:04:08 +00:00
|
|
|
# PaaS
|
2020-12-07 14:28:17 +00:00
|
|
|
awscli-cwlogs==1.4.6
|
2017-02-13 18:04:08 +00:00
|
|
|
|
2021-01-29 15:08:56 +00:00
|
|
|
git+https://github.com/alphagov/notifications-utils.git@43.8.1#egg=notifications-utils==43.8.1
|
2017-04-06 10:27:13 +01:00
|
|
|
|
2020-04-24 16:18:44 +01:00
|
|
|
# gds-metrics requires prometheseus 0.2.0, override that requirement as 0.7.1 brings significant performance gains
|
2020-12-14 11:40:07 +00:00
|
|
|
prometheus-client==0.9.0
|
2020-08-18 09:57:54 +01:00
|
|
|
gds-metrics==0.2.4
|
2020-04-20 15:59:47 +01:00
|
|
|
|
Pin all application 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.
This is based on alphagov/digitalmarketplace-api#615, so rationale
from that PR applies here.
We had a problem with unpinned packages on new deployments leading
to failed tests (e.g. alphagov/notifications-admin#2144) which is
why we're implementing this now.
After re-evaluating pipenv again, this still seems like the least
disruptive approach:
* pyup.io has experimental support for Pipfile, but doesn't respect
version ranges or updating hashes in the lock file
* CloudFoundry buildpack recognizes and supports Pipfiles out of the
box, but the support is relatively new. For example until recently
CF would install dev packages during deployment. It's also based on
generating a requirements file from the Pipfile, which doesn't
properly support pinning VCS dependencies (eg it doesn't set the
#egg= version, meaning pip will not upgrade the package if it's
already installed).
* pipenv has a strict dependency resolution algorithm, which doesn't
appear to be well documented and can cause some unexpected failures.
For example, pipenv doesn't seem to be able to install `awscli-cwlogs`
package at all, believing it to have a version conflict for `botocore`
(which it doesn't list as a direct dependency) while neither `pip` nor
`pip-tools` highlight any issues with it.
* While trying out `pipenv install` on our list of dependencies it would
regularly fail to install utils with a "Will try again." message.
While the installation succeeds after a retry, this doesn't inspire
confidence.
* The switch to Pipfile and pipenv-managed virtualenvs requires a series
of changes to `make` targets and scripts - replacing `pip install` with
`pipenv`, removing references to requirements files and prefixing
commands with `pipenv run`. While it's likely to simplify the overall
process of managing dependencies, it would require time to properly
implement across our applications and environments (Jenkins, PaaS,
docker containers, and dev machines).
2018-07-10 14:50:30 +01:00
|
|
|
## The following requirements were added by pip freeze:
|
2021-01-20 16:07:19 +00:00
|
|
|
alembic==1.5.2
|
2018-10-09 13:27:49 +01:00
|
|
|
amqp==1.4.9
|
|
|
|
|
anyjson==0.3.3
|
2020-11-06 10:56:52 +00:00
|
|
|
attrs==20.3.0
|
2021-01-29 15:08:56 +00:00
|
|
|
awscli==1.18.222
|
2020-08-18 09:57:54 +01:00
|
|
|
bcrypt==3.2.0
|
2018-10-09 13:27:49 +01:00
|
|
|
billiard==3.3.0.23
|
2020-12-07 14:28:17 +00:00
|
|
|
bleach==3.2.1
|
2020-04-20 15:59:47 +01:00
|
|
|
blinker==1.4
|
2020-02-12 15:30:02 +00:00
|
|
|
boto==2.49.0
|
2021-01-29 15:08:56 +00:00
|
|
|
boto3==1.16.62
|
|
|
|
|
botocore==1.19.62
|
2020-12-07 14:28:17 +00:00
|
|
|
certifi==2020.12.5
|
2020-12-18 14:30:39 +00:00
|
|
|
chardet==4.0.0
|
2020-04-29 15:51:02 +01:00
|
|
|
click==7.1.2
|
2020-02-12 15:30:02 +00:00
|
|
|
colorama==0.4.3
|
2020-07-31 10:36:09 +01:00
|
|
|
dnspython==1.16.0
|
2019-09-04 10:55:22 +01:00
|
|
|
docutils==0.15.2
|
2019-06-03 16:08:19 +01:00
|
|
|
flask-redis==0.4.0
|
2019-11-18 15:48:38 +00:00
|
|
|
future==0.18.2
|
2020-07-28 14:43:05 +01:00
|
|
|
geojson==2.5.0
|
2020-12-07 14:28:17 +00:00
|
|
|
govuk-bank-holidays==0.8
|
2021-01-18 10:01:45 +00:00
|
|
|
greenlet==1.0.0
|
2020-06-25 17:22:08 +01:00
|
|
|
idna==2.10
|
2021-01-18 10:01:45 +00:00
|
|
|
importlib-metadata==3.4.0
|
2020-04-14 13:08:38 +01:00
|
|
|
Jinja2==2.11.2
|
2020-05-22 10:29:16 +01:00
|
|
|
jmespath==0.10.0
|
2018-10-09 13:27:49 +01:00
|
|
|
kombu==3.0.37
|
2021-01-18 10:01:45 +00:00
|
|
|
Mako==1.1.4
|
2019-03-18 14:38:09 +00:00
|
|
|
MarkupSafe==1.1.1
|
2019-01-08 14:15:20 +00:00
|
|
|
mistune==0.8.4
|
Pin all application 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.
This is based on alphagov/digitalmarketplace-api#615, so rationale
from that PR applies here.
We had a problem with unpinned packages on new deployments leading
to failed tests (e.g. alphagov/notifications-admin#2144) which is
why we're implementing this now.
After re-evaluating pipenv again, this still seems like the least
disruptive approach:
* pyup.io has experimental support for Pipfile, but doesn't respect
version ranges or updating hashes in the lock file
* CloudFoundry buildpack recognizes and supports Pipfiles out of the
box, but the support is relatively new. For example until recently
CF would install dev packages during deployment. It's also based on
generating a requirements file from the Pipfile, which doesn't
properly support pinning VCS dependencies (eg it doesn't set the
#egg= version, meaning pip will not upgrade the package if it's
already installed).
* pipenv has a strict dependency resolution algorithm, which doesn't
appear to be well documented and can cause some unexpected failures.
For example, pipenv doesn't seem to be able to install `awscli-cwlogs`
package at all, believing it to have a version conflict for `botocore`
(which it doesn't list as a direct dependency) while neither `pip` nor
`pip-tools` highlight any issues with it.
* While trying out `pipenv install` on our list of dependencies it would
regularly fail to install utils with a "Will try again." message.
While the installation succeeds after a retry, this doesn't inspire
confidence.
* The switch to Pipfile and pipenv-managed virtualenvs requires a series
of changes to `make` targets and scripts - replacing `pip install` with
`pipenv`, removing references to requirements files and prefixing
commands with `pipenv run`. While it's likely to simplify the overall
process of managing dependencies, it would require time to properly
implement across our applications and environments (Jenkins, PaaS,
docker containers, and dev machines).
2018-07-10 14:50:30 +01:00
|
|
|
monotonic==1.5
|
2020-12-07 14:28:17 +00:00
|
|
|
orderedset==2.0.3
|
2020-12-16 15:29:06 +00:00
|
|
|
packaging==20.8
|
2021-01-29 15:08:56 +00:00
|
|
|
phonenumbers==8.12.17
|
2019-11-18 15:48:38 +00:00
|
|
|
pyasn1==0.4.8
|
2020-03-09 15:29:18 +00:00
|
|
|
pycparser==2.20
|
2020-12-07 14:28:17 +00:00
|
|
|
pyparsing==2.4.7
|
Pin all application 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.
This is based on alphagov/digitalmarketplace-api#615, so rationale
from that PR applies here.
We had a problem with unpinned packages on new deployments leading
to failed tests (e.g. alphagov/notifications-admin#2144) which is
why we're implementing this now.
After re-evaluating pipenv again, this still seems like the least
disruptive approach:
* pyup.io has experimental support for Pipfile, but doesn't respect
version ranges or updating hashes in the lock file
* CloudFoundry buildpack recognizes and supports Pipfiles out of the
box, but the support is relatively new. For example until recently
CF would install dev packages during deployment. It's also based on
generating a requirements file from the Pipfile, which doesn't
properly support pinning VCS dependencies (eg it doesn't set the
#egg= version, meaning pip will not upgrade the package if it's
already installed).
* pipenv has a strict dependency resolution algorithm, which doesn't
appear to be well documented and can cause some unexpected failures.
For example, pipenv doesn't seem to be able to install `awscli-cwlogs`
package at all, believing it to have a version conflict for `botocore`
(which it doesn't list as a direct dependency) while neither `pip` nor
`pip-tools` highlight any issues with it.
* While trying out `pipenv install` on our list of dependencies it would
regularly fail to install utils with a "Will try again." message.
While the installation succeeds after a retry, this doesn't inspire
confidence.
* The switch to Pipfile and pipenv-managed virtualenvs requires a series
of changes to `make` targets and scripts - replacing `pip install` with
`pipenv`, removing references to requirements files and prefixing
commands with `pipenv run`. While it's likely to simplify the overall
process of managing dependencies, it would require time to properly
implement across our applications and environments (Jenkins, PaaS,
docker containers, and dev machines).
2018-07-10 14:50:30 +01:00
|
|
|
PyPDF2==1.26.0
|
2020-09-14 15:21:55 +01:00
|
|
|
pyrsistent==0.17.3
|
2019-11-18 15:48:38 +00:00
|
|
|
python-dateutil==2.8.1
|
2019-02-01 09:32:43 +00:00
|
|
|
python-editor==1.0.4
|
2020-12-07 14:28:17 +00:00
|
|
|
python-json-logger==2.0.1
|
2020-12-31 12:47:03 +00:00
|
|
|
pytz==2020.5
|
2020-03-31 09:13:24 +01:00
|
|
|
PyYAML==5.3.1
|
2020-06-09 10:34:44 +01:00
|
|
|
redis==3.5.3
|
2020-12-18 14:30:39 +00:00
|
|
|
requests==2.25.1
|
2020-07-08 16:51:41 +01:00
|
|
|
rsa==4.5
|
2021-01-18 10:01:45 +00:00
|
|
|
s3transfer==0.3.4
|
2021-01-20 16:07:19 +00:00
|
|
|
Shapely==1.7.1
|
2020-05-22 10:29:16 +01:00
|
|
|
six==1.15.0
|
Pin all application 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.
This is based on alphagov/digitalmarketplace-api#615, so rationale
from that PR applies here.
We had a problem with unpinned packages on new deployments leading
to failed tests (e.g. alphagov/notifications-admin#2144) which is
why we're implementing this now.
After re-evaluating pipenv again, this still seems like the least
disruptive approach:
* pyup.io has experimental support for Pipfile, but doesn't respect
version ranges or updating hashes in the lock file
* CloudFoundry buildpack recognizes and supports Pipfiles out of the
box, but the support is relatively new. For example until recently
CF would install dev packages during deployment. It's also based on
generating a requirements file from the Pipfile, which doesn't
properly support pinning VCS dependencies (eg it doesn't set the
#egg= version, meaning pip will not upgrade the package if it's
already installed).
* pipenv has a strict dependency resolution algorithm, which doesn't
appear to be well documented and can cause some unexpected failures.
For example, pipenv doesn't seem to be able to install `awscli-cwlogs`
package at all, believing it to have a version conflict for `botocore`
(which it doesn't list as a direct dependency) while neither `pip` nor
`pip-tools` highlight any issues with it.
* While trying out `pipenv install` on our list of dependencies it would
regularly fail to install utils with a "Will try again." message.
While the installation succeeds after a retry, this doesn't inspire
confidence.
* The switch to Pipfile and pipenv-managed virtualenvs requires a series
of changes to `make` targets and scripts - replacing `pip install` with
`pipenv`, removing references to requirements files and prefixing
commands with `pipenv run`. While it's likely to simplify the overall
process of managing dependencies, it would require time to properly
implement across our applications and environments (Jenkins, PaaS,
docker containers, and dev machines).
2018-07-10 14:50:30 +01:00
|
|
|
smartypants==2.0.1
|
2021-01-18 10:01:45 +00:00
|
|
|
soupsieve==2.1
|
2019-01-08 14:15:20 +00:00
|
|
|
statsd==3.3.0
|
2020-12-18 14:30:39 +00:00
|
|
|
typing-extensions==3.7.4.3
|
2021-01-29 15:08:56 +00:00
|
|
|
urllib3==1.26.3
|
Pin all application 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.
This is based on alphagov/digitalmarketplace-api#615, so rationale
from that PR applies here.
We had a problem with unpinned packages on new deployments leading
to failed tests (e.g. alphagov/notifications-admin#2144) which is
why we're implementing this now.
After re-evaluating pipenv again, this still seems like the least
disruptive approach:
* pyup.io has experimental support for Pipfile, but doesn't respect
version ranges or updating hashes in the lock file
* CloudFoundry buildpack recognizes and supports Pipfiles out of the
box, but the support is relatively new. For example until recently
CF would install dev packages during deployment. It's also based on
generating a requirements file from the Pipfile, which doesn't
properly support pinning VCS dependencies (eg it doesn't set the
#egg= version, meaning pip will not upgrade the package if it's
already installed).
* pipenv has a strict dependency resolution algorithm, which doesn't
appear to be well documented and can cause some unexpected failures.
For example, pipenv doesn't seem to be able to install `awscli-cwlogs`
package at all, believing it to have a version conflict for `botocore`
(which it doesn't list as a direct dependency) while neither `pip` nor
`pip-tools` highlight any issues with it.
* While trying out `pipenv install` on our list of dependencies it would
regularly fail to install utils with a "Will try again." message.
While the installation succeeds after a retry, this doesn't inspire
confidence.
* The switch to Pipfile and pipenv-managed virtualenvs requires a series
of changes to `make` targets and scripts - replacing `pip install` with
`pipenv`, removing references to requirements files and prefixing
commands with `pipenv run`. While it's likely to simplify the overall
process of managing dependencies, it would require time to properly
implement across our applications and environments (Jenkins, PaaS,
docker containers, and dev machines).
2018-07-10 14:50:30 +01:00
|
|
|
webencodings==0.5.1
|
2020-04-03 13:13:57 +01:00
|
|
|
Werkzeug==1.0.1
|
2020-12-18 14:30:39 +00:00
|
|
|
zipp==3.4.0
|