I think it's generally good practice not to do from module import * and use module.foo instead, but it's inconvenient to type out pyaldata.tools.foo when we want to use a function.
It's also annoying to have to remember if some functionality is in tools or utils. Plus tools.py and utils.py are starting to be a bit too long and unorganized, so we'll have split them anyway, which will make this even worse.
What I'm thinking is that we could just export every function at the top level of the module, so that we can use pyaldata.foo without knowing if function foo is in utils.py or tools.py (or in something like utils.transformations.foo in the future).
Then we could agree on a convention for a shorthand so that we can do import pyaldata as pdt (or pld or whatever shorthand that's not pd because that's taken for pandas).
Alternatively, one might use just do from pyaldata import *. becaues I think our function names are specific enough that they don't clash with anything else and we know that they come from pyaldata
I think it's generally good practice not to do
from module import *and usemodule.fooinstead, but it's inconvenient to type outpyaldata.tools.foowhen we want to use a function. It's also annoying to have to remember if some functionality is intoolsorutils. Plustools.pyandutils.pyare starting to be a bit too long and unorganized, so we'll have split them anyway, which will make this even worse.What I'm thinking is that we could just export every function at the top level of the module, so that we can use
pyaldata.foowithout knowing if functionfoois inutils.pyortools.py(or in something likeutils.transformations.fooin the future).Then we could agree on a convention for a shorthand so that we can do
import pyaldata as pdt(orpldor whatever shorthand that's notpdbecause that's taken for pandas). Alternatively, one might use just dofrom pyaldata import *. becaues I think our function names are specific enough that they don't clash with anything else and we know that they come frompyaldata