Add requirement.txt support for freeze and install commands#30
Conversation
Saves output of modules found on connected device to a requirements.txt file in the current working directory. #29
This moves majority of existing install command to separate function and adds check for existing modules already on device. This is only checking against the names of the modules and would require further work to check versions of modules.
Adds missing install command instructions also. #29
|
I tested |
|
Hey @stevenabadie, you're on fire 🔥 👍 Thank you, once again, for this contribution. Please remember to I also took the liberty to check on the
As a result, a Other than that, it's a beauty and delighted to merge..! 🙂 |
|
@ntoll thank you for reviewing, feedback, and additions! 🙌 |
This adds support for managing project module requirements through a requirements.txt file. The freeze command can now output a requirements.txt file for all modules installed on a connected device. The install command can then use the requirements.txt file to install a list of requirements to a connected device.
The expected workflow would be that a project could export a requirements.txt file with the modules required for their project and provide the file in the project source. Another user could then quickly install all of the required modules for the project onto their device.
This is built on top of the existing install command which does not consider module versions. For later I think as there would need to be a way to organize all of the module versions.
Close #29