[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread Nathan Dunfield
William and Nick, With the default cythoning, introtest.intro.__doc__ is empty (as there is no docstring). If I invoke cython by hand with the -p option, intro.__doc__ becomes 'File: introtest.pyx (starting at line 1)' If I then copy introtest.pyx to $SAGEROOT/devel/sage, then source introsp

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread William Stein
On Mon, May 12, 2008 at 11:17 AM, Nick Alexander <[EMAIL PROTECTED]> wrote: > > > On 12-May-08, at 11:10 AM, Nathan Dunfield wrote: > > > >> Oh, that's annoying, it doesn't display the Cython command line. > >> Anyway, if you don't give the -p or --embed-positions option to > >> Cython, then

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread Nick Alexander
On 12-May-08, at 11:10 AM, Nathan Dunfield wrote: > >> Oh, that's annoying, it doesn't display the Cython command line. >> Anyway, if you don't give the -p or --embed-positions option to >> Cython, then source introspection should *not* work: > > I cython'd on the command line with the -p option

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread William Stein
On Mon, May 12, 2008 at 11:10 AM, Nathan Dunfield <[EMAIL PROTECTED]> wrote: > > > Oh, that's annoying, it doesn't display the Cython command line. > > Anyway, if you don't give the -p or --embed-positions option to > > Cython, then source introspection should *not* work: > > I cython'd on the

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread Nathan Dunfield
> Oh, that's annoying, it doesn't display the Cython command line. > Anyway, if you don't give the -p or --embed-positions option to > Cython, then source introspection should *not* work: I cython'd on the command line with the -p option and then setup.py installed. I now get a different error m

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread William Stein
On Mon, May 12, 2008 at 10:42 AM, Nathan Dunfield <[EMAIL PROTECTED]> wrote: > > > When you run the build command *precisely* what Cython and GCC > > commands are executed? I.e., touch the .pyx file, rebuild it > > and paste the build log into an email. > > William, > > It's below > > Syste

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread Nathan Dunfield
> When you run the build command *precisely* what Cython and GCC > commands are executed?  I.e., touch the .pyx file, rebuild it > and paste the build log into an email. William, It's below System: MacPro 8 core (Jan 2008) with OS 10.5 gcc: i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. b

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread Nick Alexander
On 12-May-08, at 9:47 AM, William Stein wrote: > > On Mon, May 12, 2008 at 9:45 AM, Nathan Dunfield <[EMAIL PROTECTED]> wrote: >> >> I'm working on an Cython extension module for Sage, but source code >> introspection isn't working for me. I have been seeing these introspection errors on the t

[sage-devel] Re: Problem with source introspection for a Cython extension

2008-05-12 Thread William Stein
On Mon, May 12, 2008 at 9:45 AM, Nathan Dunfield <[EMAIL PROTECTED]> wrote: > > I'm working on an Cython extension module for Sage, but source code > introspection isn't working for me. > > The extension is built from a single *.pyx file via the following > setup.py file: > > -setup.py---