-
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
Update deps and make pooch a test+docs dependency only #158
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.
Looks good except for one issue.
@@ -29,6 +29,7 @@ | |||
"import plopp as pp\n", | |||
"from ess import sans\n", | |||
"from ess import isissans as isis\n", | |||
"import ess.isissans.data # noqa: F401\n", |
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.
Using noqa
directives in the docs is not great. Can you refactor the notebook to use the imported module directly?
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.
This has already made it into other packages such as ESSdiffraction. Is it really worth the effort?
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.
The packages don't all have to be equally bad. I think it is important to keep the docs simple given our target audience. The comments are distracting. In particular because they deal with a concept (static analysers) that many users won't even know exists.
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.
I suppose we have different opinions on this: Having to use a module imported under an additional different name is likewise increasing the cognitive overhead. I think most users never even look at the cell doing module imports, they are more likely to look at the code further down.
If you feel really strongly about this, please push an update.
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.
I can push an update, I also think it's cleaner without the noqa
;-)
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.
Update: having gone through the different notebooks and started making the changes, I am changing my mind on this. I now agree that it's more confusing to have two different modules to get things from, and only remembering one is easier.
In addition, this may all change again if we make a separate common essdata
package, so minimizing the number of changes here by adding the noqa import line is fine I think.
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.
Ok
No description provided.