Migrates to Pipenv. The default virtual environment pollutes my file system. The requirements.txt file is a pain to manage. PyUp.io doesn't work for GitHub Enterprise when SAML is turned on, so we can't use that anymore to upgrade requirements.txt. But if we use Pipenv we can just run pipenv update once a month and it will upgrade the Pipfile.lock. That would be much easier, I think.
I manage several OSS repositories that all follow the same project scaffolding and automation. This is the first major OSS repository that I'm migrating this to, so there might be a hiccup in automation. I used Pipenv for Policy Sentry and Cloudsplaining previously though, so the migration back to it should be fairly straightforward.
What gif best describes this PR or how it makes you feel?
What does this PR do?
pipenv updateonce a month and it will upgrade the Pipfile.lock. That would be much easier, I think.I manage several OSS repositories that all follow the same project scaffolding and automation. This is the first major OSS repository that I'm migrating this to, so there might be a hiccup in automation. I used Pipenv for Policy Sentry and Cloudsplaining previously though, so the migration back to it should be fairly straightforward.
What gif best describes this PR or how it makes you feel?
Completion checklist