#15985: Python 3 preparation: Fix implicit relative imports (from sibling
modules)
-------------------------------------+-------------------------------------
Reporter: wluebbe | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.2
Component: distribution | Resolution:
Keywords: python3 | Merged in:
Authors: Wilfried Luebbe | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/ohanar/relative_imports | 19692cba6ef085f5563f4302f34d6cb5c9a281e5
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ohanar):
So it looks like the issue that you are getting into is the wonder that is
affectionately referred to as Sage's import hell :).
Looking at the traceback, it looks like the issue is a circular import
that mysteriously works right now: `sage.rings.rational` imports something
from `sage.rings.fast_arith` which imports something from
`sage.rings.integer_ring` which imports something from
`sage.rings.rational_field` which imports `sage.rings.rational`.
This is one of the big reasons why Sage is not truly usable as a python
library, because the order in which you import Sage is incredibly
delicate, and seems to magically work (and as you can see from this patch
which shouldn't change anything, it truly is magical). There hasn't been
much effort to fix this, but I would say that getting Python 3 working is
a pretty big motivator.
--
Ticket URL: <http://trac.sagemath.org/ticket/15985#comment:7>
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.
