#15351: import_statements sometimes fails
-------------------------------------+-------------------------------------
Reporter: vdelecroix | Owner: vdelecroix
Type: defect | Status: needs_work
Priority: major | Milestone: sage-6.2
Component: misc | Resolution:
Keywords: | Merged in:
Authors: Vincent Delecroix | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vdelecroix/improve_import_statements|
815320ea5e5f3dd58d195599e0da620e67906cc1
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Hi,
Thanks so much for telling me to rewrite it ! Now it is simpler and
cleaner and I hope you will understand everything.
I do have two things to solve before getting this in a needs-review status
* try to not load extra modules in the function `find_objects_from_name`
(see the [[https://groups.google.com/forum/#!topic/sage-
devel/Ok0s5ViT9dA|thread on sage-devel]])
* possibly move the functions `find_objects_from_name` and
`find_object_modules` in `sage.misc.sageinspect`
See you soooooooooooon
--
Ticket URL: <http://trac.sagemath.org/ticket/15351#comment:13>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
