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
improve import_statements #12543
Comments
Changed author from Nicolas Thiery to Vincent Delecroix |
Changed keywords from none to import_statements, development |
This comment has been minimized.
This comment has been minimized.
videlec
changed the title
import_statementss combined with search_def
improve import_statements
Jan 27, 2013
comment:2
Now, all function in the module are documented... |
Reviewer: Nicolas M. Thiéry |
This comment has been minimized.
This comment has been minimized.
comment:3
Attachment: trac_12543-import_statements-vd.patch.gz I did some improvements with Vincent watching over my shoulder. Positive review! Thanks Vincent :-) |
Merged: sage-5.8.beta3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, import_statements yields a name error if the class is not
imported in the Sage interpreter namespace. For example.
With this patch, one can specify the object as a string, and the object
is looked up in all (imported) Sage modules.
See the documentation for more examples.
This patch implements several heuristics to better handle ambiguous
names.
CC: @sagetrac-sage-combinat
Component: misc
Keywords: import_statements, development
Author: Vincent Delecroix
Reviewer: Nicolas M. Thiéry
Merged: sage-5.8.beta3
Issue created by migration from https://trac.sagemath.org/ticket/12543
The text was updated successfully, but these errors were encountered: