#18083: Stop using old_style_globals
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.6
Component: cython | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/stop_using_old_style_globals|
9ccd889321d311903d4ab26449e6dd8154879aee
Dependencies: #12446, #18084 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:13 nbruin]:
> Replying to [comment:12 jdemeyer]:
> > That was exactly my question: how?
> Logically the (very thin!) wrapper `cython` might be injected into the
same global scope as inject is written in.
Sorry, I don't understand this sentence.
> Alternatively, once "inject" has been defined, we could inject it:
> {{{
> sage.misc.cython.inject = inject #we don't need cython_c anymore
> }}}
So everybody's Sage code should start with the boilerplate
{{{
sage.calculus.var.inject = inject
sage.calculus.function.inject = inject
sage.calculus.desolver.inject = inject
sage.misc.cython.inject = inject
sage.misc.fortran.inject = inject
}}}
Not an elegant solution. Of course you could say "let's define `inject` in
just one place" and call it from there, which is essentially my proposal.
--
Ticket URL: <http://trac.sagemath.org/ticket/18083#comment:14>
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.
