feat: add requirements_freeze.txt file to help lock down a working environment #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
The
requirements_freeze.txt
provides a complete list of installed package versions and dependencies of a known working environment. This provides a reference to revert to if therequirements.txt
file generates an unusable environment in the future. Additional discussion can be found in the closed PR here:#147
What is the code doing
In order to standardize the environment that the freeze file is generates in, I used a Python:3.65 docker image found here:
https://hub.docker.com/_/python
I didn't see much in the way of extra packages compared to conda.
The code used to automatically generate this file is within this branch:
https://github.com/intvenlab/PowerSimData/compare/dependency_docker_generation
Time to review
30min