[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-20 Thread kcrisman
> > Is this the thread? > > >http://groups.google.com/group/sage-devel/browse_thread/thread/70eb8b... > > Much > older:http://trac.sagemath.org/sage_trac/attachment/ticket/4986/import-audi... I never saw this reply until Leif resurrected this thread. Is that patch still workable? That is, sho

[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-20 Thread Volker Braun
No, I haven't. And I'm off to sleep now since I have to catch an early flight tomorrow ;-) -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http:

[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-20 Thread leif
On 6 Aug., 18:32, William Stein wrote: > On Sat, Aug 6, 2011 at 2:21 AM, Volker Braun wrote: > > When I tried to remove the --disable-function-redefinition, I got lots of > > failures from the Sage library. This is not unexpected, as the release notes > > state. I tried to clean up some of the ci

Re: [sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-06 Thread William Stein
On Sat, Aug 6, 2011 at 2:21 AM, Volker Braun wrote: > On Friday, August 5, 2011 9:10:12 PM UTC+1, kcrisman wrote: >> >> [...] this is because Cython puts a lot of cimport and >> other stuff long before the "regular" stuff in the C file. > > Slightly OT, but I recently noticed that Sage is using cy

[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-06 Thread leif
On 5 Aug., 23:07, Robert Bradshaw wrote: > On Fri, Aug 5, 2011 at 1:10 PM, kcrisman wrote: > > The problem occurs in a (to me) odd spot.  Namely, in sage/misc/ > > functional.py, there is an import of CDF.  Print statements show that > > - all inside this one line! - we initialize PariInstance, g

[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-06 Thread Volker Braun
On Friday, August 5, 2011 9:10:12 PM UTC+1, kcrisman wrote: > > [...] this is because Cython puts a lot of cimport and > other stuff long before the "regular" stuff in the C file. > Slightly OT, but I recently noticed that Sage is using cython --disable-function-redefinition. The http://wiki.c

Re: [sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-05 Thread Robert Bradshaw
On Fri, Aug 5, 2011 at 9:00 PM, kcrisman wrote: > >> > > But I don't know enough about the order that these things happen in, >> > > nor how to tell that from the C file, to trace it all out.  Can >> > > someone give me a sense - or show me enough of how to do it so I can >> > > do it myself - how

[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-05 Thread kcrisman
> > > But I don't know enough about the order that these things happen in, > > > nor how to tell that from the C file, to trace it all out.  Can > > > someone give me a sense - or show me enough of how to do it so I can > > > do it myself - how to track what's being done in complex_number. > > > {

[sage-devel] Re: How to trace what happens in imports in a pyx file

2011-08-05 Thread kcrisman
On Aug 5, 5:07 pm, Robert Bradshaw wrote: > On Fri, Aug 5, 2011 at 1:10 PM, kcrisman wrote: > > Recently, Leif and I have been trying to track down #11551 (Pari > > segfaults on startup in Cygwin). > > > The problem occurs in a (to me) odd spot.  Namely, in sage/misc/ > > functional.py, there i