At the top level python_cc_readerdirectory live the user-level scripts such as library_levels.py and beautify_changed_files_in_branch.py. Within the lower level python_cc_reader/python_cc_reader directories live the modules that actually do all the heavy lifting.
These scripts are imported by a number of other scripts in the tools repository, and I have updated all of these scripts.
My intention is to create this PR as a permanent record of the merge to master which I am going to make immediately after opening this PR. I will merge this to master in the tools repository, and then I will be merging a PR in the main repository (PR 4590) that updates the tools submodule immediately afterwards.
This PR massively reshapes the python_cc_reader module as this module is converted to python3.
The directory structure is as follows:
The rationale for this dirname-within-dirname structure was given on this page:
https://docs.python-guide.org/writing/structure/
At the top level
python_cc_reader
directory live the user-level scripts such aslibrary_levels.py
andbeautify_changed_files_in_branch.py.
Within the lower levelpython_cc_reader/python_cc_reader
directories live the modules that actually do all the heavy lifting.These scripts are imported by a number of other scripts in the
tools
repository, and I have updated all of these scripts.My intention is to create this PR as a permanent record of the merge to master which I am going to make immediately after opening this PR. I will merge this to master in the
tools
repository, and then I will be merging a PR in themain
repository (PR 4590) that updates thetools
submodule immediately afterwards.