#13864: Configure Python with pydebug when SAGE_DEBUG is set
-------------------------------------+--------------------------------------
Reporter: jpflori | Owner: jason
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-5.6
Component: misc | Resolution:
Keywords: python spkg | Work issues:
Report Upstream: N/A | Reviewers: Volker Braun
Authors: Jean-Pierre Flori | Merged in:
Dependencies: #13865 | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by jpflori):
Replying to [comment:37 vbraun]:
> Yes you can't do any arithmetic while the circular import is still on
its way.
If I had statements at the end of integer_ring.pyx and integer.pyx they
get executed before all this mess, so I thought that in this case it was
not a circular import problem.
> For starters it invokes coercion so its a huge mess.
I don't see any coercion involved, where did you spot it?
> The following lets me get past it
> {{{
> big = Integer('340282366920938463463374607431768211457') # two**128 +
one
> }}}
> Of course it dies in the next place where stupid computations are
performed upon import.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13864#comment:41>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
