-
-
Notifications
You must be signed in to change notification settings - Fork 295
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
__getattr__ shortcut for calling GRASS display modules #1723
__getattr__ shortcut for calling GRASS display modules #1723
Conversation
|
There are a couple things that need improvement still:
|
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.
Sweet and simple, just the error handling needs some more work.
Please, include an example in the notebook, so that others can try easily.
…haedri/grass into non-interactive-display-update
|
@chaedri It seems to me that the message "Module must begin with 'd_'" needs little more clarification, but let's leave that for some documentation PR. (I'm thinking module vs GRASS module, "must begin with" vs display commands, and including the name of the command. |
…OSGeo#1723) Shortcut allowing users to call GRASS display modules (d.*) with method .d_*. Method name must start with d and underscore and it needs to be an executable on path, other error handling is left to the underlying functions. Example is in the Jupyter integration notebook.
…OSGeo#1723) Shortcut allowing users to call GRASS display modules (d.*) with method .d_*. Method name must start with d and underscore and it needs to be an executable on path, other error handling is left to the underlying functions. Example is in the Jupyter integration notebook.
…OSGeo#1723) Shortcut allowing users to call GRASS display modules (d.*) with method .d_*. Method name must start with d and underscore and it needs to be an executable on path, other error handling is left to the underlying functions. Example is in the Jupyter integration notebook.
.d_*.These modifications are part of an on-going Google Summer of Code project, Improved Integration of GRASS GIS and Jupyter Notebooks. You can find more information here. You can test out the functionality in Binder here:
https://mybinder.org/v2/gh/chaedri/grass/non-interactive-display-update?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks%2Fjupyter_integration.ipynb