Closed ryanhassing closed 4 years ago
I thought this PR was supposed to be exclusively for package management. Why is this forked from the database implementation branch? Merge the database branch into master first, and then update this branch to purely do package management.
The branch is forked from master. Are you asking to remove the database submodule? And work on that via the database branch? @enioluwa23
Ryan, theres a few conflicts in the branch. Did you pull from master branch so that you would get the updated SRS_Cycle2.docx?
Ryan, theres a few conflicts in the branch. Did you pull from master branch so that you would get the updated SRS_Cycle2.docx?
Resolved. Sorry about that.
@enioluwa23 / @Juan-Garcia96 , resolved all conflicts and removed database code. I left the core
directory in, just to be safe. We can move code over from there to src/chariot
in the future, then we can drop core
.
Any other issues?
System backend is setup as a Python package, with top level
chariot/src/chariot
.I've included instructions to run and import modules in the file RUNNING_MODULES.md. I'm not sure if these instructions should be added to the README or the CONTRIBUTING document, but we can do that in the future.
I've updated the import statements for all backend code. Check any file in the package to see the new import format, and use that going forward. I've also added
__pycache__/
and '.py[cod]' to the `.gitignore', to keep compiled files out of the repo.After merging this branch, all backend code should be relocated to the
chariot/src/chariot
directory.