Using pip-tools to manage dependencies

Currently zappa has several pinned dependencies that make it likely that it works, but also makes it hard to keep using as time passes because of other packages dependency updates.

For this I believe we should be separating the hard requirements from the pinned ones.

pip-tools allows us to do that, while not having two collections of requirements that need to be updated individually.

Context

See many complaints throughout the years.

Expected Behavior

Installing zappa should work with an open-ended set of dependencies until a specific one doesn’t work.

Actual Behavior

Some installations only work if people ignore the dependency requirements.

Possible Fix

With pip-tools, updating a requirement would be adding it in requirements.in or test_requirements.in as needed and then running:

pip-compile -o test_requirements.txt requirements.in test_requirements.in && cp test_requirements.txt requirements.txt && pip-compile -o requirements.txt requirements.in

[gopalmeena]

I have not used this package manager poetry, but it seems that poetry keeps things simple and clean to use. I hope this may help.

[jneves]

@monkut tried it with zappa - ended up with a broken set of incompatible packages and, even if worked, would be limited to 2 sets of dependencies when I want at least 3 in the end (production, tests and dev)