Problems solved -- it was the indentation level. My new function was
indented too much so was being defined within the scope of the
function above it instead of in the class scope.
All now works.
I expect I'll get used to using indentation instead of {...} for
scoping eventually!
John
PS I'm always amused by the ads which gmail chooses to display on the
right side of the window. For this thread the first one is:
Wasting your C++ Talents?
Looking for a more demanding role? You have found it. Apply now!
www.igence.com
which was funny since I was *thinking* about all the C++ skills I have
which I am having to unlearn but had not written that. Perhaps Big
Brother Google can now read our thoughts too!
On 25/01/2008, David Joyner <[EMAIL PROTECTED]> wrote:
>
> My wild guess, knowing nothing at all about what you are trying to do,
> is that either you have a import problem of some type. In any case,
> I would try cutting out the new code and putting it in a test.sage
> file then using
> attach to check for errors.
>
> On Jan 25, 2008 12:09 PM, John Cremona <[EMAIL PROTECTED]> wrote:
> > To answer Mike first: yes, I'm working in a clone (branch) called
> > eciso and also running that branch. Here's the output of "sage -br"
> >
> > [EMAIL PROTECTED] -br
> >
> > ----------------------------------------------------------
> > sage: Building and installing modified SAGE library files.
> >
> >
> > Installing c_lib
> > scons: `install' is up to date.
> > running install
> > running build
> > running build_py
> > copying sage/schemes/elliptic_curves/ell_generic.py ->
> > build/lib.linux-i686-2.5/sage/schemes/elliptic_curves
> > running build_ext
> > running build_scripts
> > running install_lib
> > copying build/lib.linux-i686-2.5/sage/schemes/elliptic_curves/ell_generic.py
> > ->
> > /home/src/sage/local/lib/python2.5/site-packages/sage/schemes/elliptic_curves
> > byte-compiling
> > /home/src/sage/local/lib/python2.5/site-packages/sage/schemes/elliptic_curves/ell_generic.py
> > to ell_generic.pyc
> > running install_scripts
> > changing mode of /home/src/sage/local/bin/dsage_server.py to 755
> > changing mode of /home/src/sage/local/bin/dsage_worker.py to 755
> > changing mode of /home/src/sage/local/bin/dsage_setup.py to 755
> > running install_data
> > running install_egg_info
> > Removing
> > /home/src/sage/local/lib/python2.5/site-packages/sage-0.0.0-py2.5.egg-info
> > Writing
> > /home/src/sage/local/lib/python2.5/site-packages/sage-0.0.0-py2.5.egg-info
> > ----------------------------------------------------------------------
> > | SAGE Version 2.9.3, Release Date: 2008-01-05 |
> > | Type notebook() for the GUI, and license() for information. |
> > ----------------------------------------------------------------------
> > Loading SAGE library. Current Mercurial branch is: eciso
> > Reading JEC's version of weierstrass_morphism.py
> > Reading JEC's version of ell_generic.py
> > sage:
> >
> > As you can see, (1) I am running by branch, and (2) I aded print
> > statements to the files I was editing to make sure that exactly those
> > were read in (each branch has no less than 4 copies of each .py file
> > for some reason...)
> >
> > I have attached the current version of ell_generic.py but it will not
> > work without the correspondingly changed weierstrass_morphism.py.
> >
> > John
> >
> > On 25/01/2008, Mike Hansen <[EMAIL PROTECTED]> wrote:
> > >
> > > > Help!
> > >
> > > I'm not sure if you use branches or not, but if you do, you might want
> > > to make sure that the file you're editing is in the same branch as the
> > > one Sage is running.
> > >
> > > --Mike
> > >
> > > >
> > >
> >
> >
> > --
> > John Cremona
> >
> >
> > >
> >
>
> >
>
--
John Cremona
--~--~---------~--~----~------------~-------~--~----~
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-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
