Closed hershal closed 7 years ago
Also we should remove all dangling files which are not used anywhere.
Do you have a classy way to detect these dangers?
Weird, this didn't close from your comment, even though it looks like it would have in a commit :confused:
Good question. Maybe a static analysis tool would do this? pyreverse
comes to mind because it generates a graph of python modules, but I'm not sure this would work properly since our entry point is currently through the tests...
These files are named incredibly stupidly and take way too long to type out. The class names should be the only long-ish names, so that they are distinguished clearly in code. The filenames, however, need not be so long.
E.g. this
could be simplified to