1137023 - [12fa] Explicitly declare and isolate dependencies

Status: RESOLVED FIXED

(Input Graveyard :: Backend, defect)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Our server environments have some dependencies installed on them that may not be specified in requirements files.

This bug covers:

1. making sure the requirements files specify *ALL* Python dependencies--compiled and otherwise

2. making sure there aren't dependencies that shouldn't be in there that might be holdovers from the Playdoh days

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Under bug #1048462, I did the following work:

1. converted as many github url based requirements to PyPI based requirements

2. added version numbers to all github url based requirements so they update
   correctly going forward using peep

3. removed Playdoh hold-overs and other requirements we weren't using with the exception
   of django-sha2/python-bcrypt--pretty sure we can remove that, but it could be
   somewhat involved

This morning, I made sure the requirements files cover all Python dependencies.

The vagrant_provision.sh script installs the system packages for pip and virtualenv. Those are the only two exceptions to the above, but they'd be used for provisioning and possibly deployment--not running the software.

That covers everything in this bug, so I'm closing this one out.

It was about 1 point of additional work here above and beyond bug #1048462.