inspect4py
inspect4py copied to clipboard
SoftwareUnderstanding
Static code analysis package for Python repositories
It would be great to suggest this using already existing models. Maybe we can tweak something existing already
The repository with the build instructions is old (before we converted code_inspector into a package)
There are repositories that create packages that do not use setup.py/cfg to create them - Instead, they use customize scripts, such as "install.py". Example, [autojump](https://github.com/wting/autojump/blob/master/install.py). Our current heuristic does not...
The [rtdl](https://github.com/yandex-research/rtdl) repository has a setup.cfg, but it is not used. Should we annotated it as a library, or as script? The repo classifies itself as a library, but looking...
Options: 1. store the module that the console script calls to --> setup_info["run"].append("python -m " + cs_run ) 2. store the console script name --> setup_info["run"].append(cs_string ) Example - lets...
Right now these are only returned in scripts with main. However, for the ranking it would be beneficial to include if services and scripts with body also have this info
The call graph is now not part of the JSON as a single object. Plus, it's a call list, and we want to convert it to a graph.
The evaluation has hardcoded paths, which is not great. I should make them proper inputs
We have it for 3.X, but for 3.9.5 I had to remove `==2.3.2` from cdmcfparser. We should make sure it works in python 3.6 .. 3.9
This may be a project in itself. The idea would be to turn a project with a script/series of scripts into a package, based on what we know.
Metadata
Owner
Metadata
Static code analysis package for Python repositories