Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Events package structure question #141

Closed
aaraney opened this issue Oct 26, 2021 · 3 comments
Closed

Events package structure question #141

aaraney opened this issue Oct 26, 2021 · 3 comments

Comments

@aaraney
Copy link
Member

aaraney commented Oct 26, 2021

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 the event_detection directory but not in the events directory. @jarq6c can you clarify why this is the case? I assume there should be an __init__.py in the events directory as well.

Thanks!

@jarq6c
Copy link
Collaborator

jarq6c commented Oct 27, 2021

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.

@aaraney
Copy link
Member Author

aaraney commented Oct 29, 2021

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.

@jarq6c
Copy link
Collaborator

jarq6c commented Nov 3, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants