#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):
Can I read this proposal as:[[br]]
Do the (absolute) imports as {{{import sage.somewhere.amodule as am}}} and
then use it as {{{am.a_function(a_parm)}}}.
Perhaps the module could recommend its "standard" abbreviation (here
{{{am}}}). Such a convention might help while reading code that uses the
module.
--
Ticket URL: <http://trac.sagemath.org/ticket/15985#comment:11>
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.
