Open aaraney opened 3 years ago
I think we had originally discussed adding various subpackages under events
, but we never decided if events
was going to be a proper package or another namespace package.
Do you have an opinion on the future of the events
package? I am happy to retain it as it's own namespace package (as it is now). However, I am equally happy to keep it the way it is for flexibility in the future.
No strong opinions at this point. My preference might be to leave it, unless there's a compelling reason to change it. I would rather future development guide what we do, say when/if different event based analysis methods get added like events.event_analysis
or the like.
I noticed while looking around the package today that the
event_detection
module is nested one level deeper than typical and does not have a parent subsubpackage (directory above with__init__.py
).More concretely, on the path
hydrotools/python/events/src/hydrotools/events/event_detection/
, there is an__init__.py
in theevent_detection
directory but not in theevents
directory. @jarq6c can you clarify why this is the case? I assume there should be an__init__.py
in theevents
directory as well.Thanks!