Idea is that for each group of related code create a subpackage namespace containing following within the library directory. Try to group related functionality into the same subpackage namespace along with correlating test files. Each directory should contain:
[ ] README with a description of package contents (github will render these from the directory view just as it would with the repo's main page)
[ ] specifically named files containing code (convolve.py) (try to avoid generic names like utils.py)
[ ] corresponding test file (convolve_test.py)
[ ] directory containing any package specific test data (more general data can just be stored in a directory called data in the root directory)
I'm not sure if this will play nice with how python handles namespaces or you could run into some cyclic dependency problems. This is something you may want to wait to do until after getting more code covered.
Idea is that for each group of related code create a subpackage namespace containing following within the library directory. Try to group related functionality into the same subpackage namespace along with correlating test files. Each directory should contain:
datain the root directory)I'm not sure if this will play nice with how python handles namespaces or you could run into some cyclic dependency problems. This is something you may want to wait to do until after getting more code covered.