You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2020. It is now read-only.
why are the core parts of file, utils, etc named as nwb_XXX? It seems unnecessary given that the main package is already called nwb, and in the examples when they're imported, they are already renamed w/ import nwb.nwb_utils as utils. Maybe this is a minor point but it'd be good to streamline the API to follow conventions of other major python projects in the numpy ecosystem
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
why are the core parts of
file
,utils
, etc named asnwb_XXX
? It seems unnecessary given that the main package is already callednwb
, and in the examples when they're imported, they are already renamed w/import nwb.nwb_utils as utils
. Maybe this is a minor point but it'd be good to streamline the API to follow conventions of other major python projects in the numpy ecosystemThe text was updated successfully, but these errors were encountered: