The guiding idea was to add more data at the stage of the experiment run to be able to filter and transform it on the later stages of the analysis.
This PR introduces:
metadata of the FD run:
project_name
fawltydeps_version, also the version is bumped. Every time we change the schema of the results of the way they are computed, we should bump the last number in the version. This way we know that we branched out at version 0.13.1 from the original FD, and still have a version for the experiment.
repo_url - added in the execution stage (PyPI_analysis/download_and_analyze.py)
creation_timestamp- added in the execution stage (PyPI_analysis/download_and_analyze.py)
Add information about all imports.
Collection numbers of .py and .ipynb files per each directory. Note here, that the number always represents .py or .ipynb files that are directly contained in the directory. This example:
This PR may be checked commit by commit.
The guiding idea was to add more data at the stage of the experiment run to be able to filter and transform it on the later stages of the analysis.
This PR introduces:
project_name
fawltydeps_version
, also the version is bumped. Every time we change the schema of the results of the way they are computed, we should bump the last number in the version. This way we know that we branched out at version 0.13.1 from the original FD, and still have a version for the experiment.repo_url
- added in the execution stage (PyPI_analysis/download_and_analyze.py)creation_timestamp
- added in the execution stage (PyPI_analysis/download_and_analyze.py).py
and.ipynb
files per each directory. Note here, that the number always represents.py
or.ipynb
files that are directly contained in the directory. This example:will give us:
For the reference - result of the run on FawltyDeps