#13083: Import fails in sage-python
----------------------------+-----------------------------------------------
Reporter: poeschko | Owner: GeorgSWeber
Type: defect | Status: new
Priority: major | Milestone:
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
----------------------------+-----------------------------------------------
Comment (by hivert):
Replying to [comment:1 mhansen]:
> Before you can do any of those specific imports, you need to do
>
> {{{
> import sage.all
> }}}
>
> which will import things in the correct order and make sure everything
is initialized. After that, you can import what you need.
I think this nevertheless witnesses some problems with Sage's imports and
modularity. Is there a good reason why this shouldn't work ?
Florent
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13083#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
