#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):
As your numbers indicate (and from my personal experience), there is
definitely an unofficial convention to use absolute from..import
statements in the sage library, i.e. `from sage.foo import bar`; however
this is one of (if not the main) culprit behind the circular import issues
of the Sage library. A lot of the circular import issues could be resolved
by just importing a module, and not particular attributes of the module
(i.e. using `import sage.foo` or `import sage.foo as bar` and using
`sage.foo.baz`/`bar.baz` instead of `from sage.foo import baz`).
--
Ticket URL: <http://trac.sagemath.org/ticket/15985#comment:10>
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.
