#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 wluebbe):
Some numbers:
||lines with "import"|| 26,3231||
||- thereof lines with "from sage"|| 19,581||
||- thereof lines with "import sage"|| 1,650||
||leaving lines with imports from Python [[br]]standard library and
implicit relative import[[br]](and 1 explicit relative import :-)|| about
5,000||
Questions:
* Is there agreement in the Sage community that absolute import is the way
to go?
* Can it help with the above {{{ImportError}}}? And similar ones?
* Other benefits or drawbacks?
--
Ticket URL: <http://trac.sagemath.org/ticket/15985#comment:9>
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.
