Previously, the mol_toolkits directory called our default mol_toolkit instead I've written a file mol_toolkits.py that acts as a "factory". Creating factory methods has been my plan for a while, thanks to a suggestion from @dgasmith last spring. However, at the time I couldn't figure out how to handle the different imports.
This factory class is more flexible than the initial implementation. It will allow users to provide molecules from anywhere in any of the other modules without knowing internally we are working with our own data structures.
While this isn't ideal, I'm going to go ahead and merge this because the tests are passing and this was largely just a way to move code around, not anything new.
Previously, the mol_toolkits directory called our default
mol_toolkit
instead I've written a filemol_toolkits.py
that acts as a "factory". Creating factory methods has been my plan for a while, thanks to a suggestion from @dgasmith last spring. However, at the time I couldn't figure out how to handle the different imports.This factory class is more flexible than the initial implementation. It will allow users to provide molecules from anywhere in any of the other modules without knowing internally we are working with our own data structures.