coinbase
Complete requirements parsing/processing for Python
Per {this}, it seems like the current story for python package information is reading the requirements.txt file. Often times, we find that when developers don't practice proper dependency management, this file is not really the source of truth for all packages that are pulled into the build artifact. With that being said, is there something on the roadmap to parse the contents of the virtualenv and the collection of system level installed python packages?
Thanks for the issue. This is very relevant.
Currently there is nothing on the road map relating to this, but it does seem like a good idea. If you have the time and a good handle on how to do this, feel free to make make a PR.
Otherwise, do you mind elaborating a bit more on the situation and what's required. Then we can turn this into an enhancement ticket that someone might pick up.
