[sage-devel] Re: discovering the code actually executed

2015-03-10 Thread mmarco
The trace command only shows python code (it is actually an interface to the python debugger). The cython parts are skipped. That is why you see directly the ideal.is_prime() call without seeing the cython code that called it. I wonder if it could be possible to have something that mixes cython

[sage-devel] Re: discovering the code actually executed

2015-03-10 Thread Dima Pasechnik
On 2015-03-10, Justin C. Walker wrote: > > On Mar 9, 2015, at 07:43 , Dima Pasechnik wrote: > >> On 2015-03-09, Justin C. Walker wrote: >>> >>> On Mar 9, 2015, at 05:09 , Dima Pasechnik wrote: >>> So far I was able to do this manually, but I am really stuck trying to figure out e.g. w

Re: [sage-devel] Re: discovering the code actually executed

2015-03-09 Thread Justin C. Walker
On Mar 9, 2015, at 07:43 , Dima Pasechnik wrote: > On 2015-03-09, Justin C. Walker wrote: >> >> On Mar 9, 2015, at 05:09 , Dima Pasechnik wrote: >> >>> So far I was able to do this manually, but I am really stuck trying to >>> figure out e.g. what happens upon calling >>> >>> sage: QQ(2).is_p

[sage-devel] Re: discovering the code actually executed

2015-03-09 Thread Dima Pasechnik
On 2015-03-09, Justin C. Walker wrote: > > On Mar 9, 2015, at 05:09 , Dima Pasechnik wrote: > >> So far I was able to do this manually, but I am really stuck trying to >> figure out e.g. what happens upon calling >> >> sage: QQ(2).is_prime() >> >> I vaguely recall seeing discussions and tips how