New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add version-listing tool #1
Conversation
I agree keeping track of dependencies is useful. And is it possible to specify this ahead of time with a requirements.txt? |
I think there are a few problems with this idea:
|
What about tagging the commit that produced major outputs and then sticking the repo and tag ID in the metadata? That seems like the "industry standard" way to do this for non-released packages, right? Then you have the package dependencies in the repo, and then include in the output file's metadata the repo url, the tag ID, and the data dependencies. That provides exactly how much information you need to reproduce the results, right? |
The goal of this was to make the process of recording accurate dependencies easier. Unless I misunderstand it, your proposal seems strictly less easy than filling it out by hand and equally error-prone. |
Thanks! I shared the changes you made with Jong-kai. |
Finds the installed module versions and git repository hashes of a set of modules, to be included in output file dependencies.