Help a user report the env variables when creating an issue
In case of an issue, the user could run a script to give us a detailed environment information. For example the version of retriever installed, the interpreter used, (core python, Conda distribution), version of packages, and path where packages are loaded, etc. This will enable the team to reproduce and issue or error.
I love this idea. As I mentioned over in https://github.com/weecology/Retriever.jl/pull/27, I wonder if the best solution isn't a new retriever command like retriever env or even a flag like retriever --report install sqlite breed-bird-survey. Another option would be to leverage the existing --debug flag and have it great one or more log files with all of the necessary information.
Since it is not common for the retriever installation to fail, we should add the environment reporting scripts to the retriever.
The script should report based on the desired environment. For example, if we want variables under the julia environment or R environment or even Python. If an edge case happens, someone could download the script and run it independent of the retriever.
@henrykironde @ethanwhite Can I try working on the scripts?
Sure @ashishpriyadarshiCIC go for it