-
Notifications
You must be signed in to change notification settings - Fork 2
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
Make namespace package #113
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we ready to drop the support for installing esssans and old ess in the same env?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does isissans
need to be a separate package? Doesn't it make more sense to have ess.sans.isis
? The isis stuff is temporary anyway, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I don't really know, I thought because it's temporary then maybe easier to pull it out of ess.sans
?
As a side note, I named it isissans
because I thought from ess import isis
didn't make much sense, since it was just SANS-related stuff.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I don't really know, I thought because it's temporary then maybe easier to pull it out of ess.sans?
Dunno. I'm fine with it either way.
As a side note, I named it isissans because I thought from ess import isis didn't make much sense, since it was just SANS-related stuff.
👍
I think so? I don't think anyone is using sans and other old ess things at the same time. |
Fixes #87