#4366: sys.path is searched ("stat"ed) for *.pyx-files insanely often
-------------------------+--------------------------------------------------
Reporter: GeorgSWeber | Owner: GeorgSWeber
Type: defect | Status: assigned
Priority: major | Milestone: sage-3.2
Component: coercion | Resolution:
Keywords: |
-------------------------+--------------------------------------------------
Comment (by robertwb):
Coincidentally, I just responded to this thread on sage-devel. I'll repost
here
{{{
Thanks for tracking this down. Just out of curiosity, how does one decide
if one "really wants to." Ideally one could snapshot the traceback without
touching every file involved.
BTW, using RDF rather than float will be 10x faster in this case even
after your speedup.
sage: sage: time for i in range(10^4): RDF(1)/2
CPU times: user 0.03 s, sys: 0.00 s, total: 0.03 s
Wall time: 0.03 s
- Robert
}}}
The point is that when something goes wrong, one wants to be able to ask
"what happened" which is why these tracebacks are stored. Re-running the
command may not give you all the information because of the caching
involved. Is there a better way to get the traceback information than
invoking sys.exc_info?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4366#comment:4>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
