[sage-devel] Re: Why is the Groebner basis not an ideal

[David Kohel]

> OK, as a conscious decision it is certainly justified. Of course,
> mathematically you are right that an object and a particular basis of
> that object are two different things. Only i was surprised, because i
> grew up with Singular and not with Magma...

FYI, magma has both commands GroebnerBasis, which returns
a sequence, and Groebner, which is actually a procedure that
modifies the ideal basis in place so that

Basis(Groebner(I)) eq GroebnerBasis(I);

returns true.  Interestingly, the syntax is not Groebner(~I), which
is what one would expect for a call-by-reference, modifying the
object in place.  But that seems to be a design decision that the
user-defined ideal generators are not an immutable attribute of
the ideal, so GroebnerBasis also changes the ideal generators
in place.

--David


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] jsMath fonts

[Jason Grout]

There has been some discussion about including the computer modern 
jsMath fonts in Sage to ease installation.  The license agreement for 
these fonts is:


The author of this fonts grants to any individual or non-commercial
organization the right to use and to make an unlimited number of copies of
full package or selected fonts when this is done WITHOUT CHARGE
and has attached this file with licence agreement.

This fonts cannot be sold or distributed with any commercial product or 
used
in any commercial organization without additional agreement with author.
If you want to charge a small fee via distribution these fonts
or any derivations from this fonts, you should contact the author.

This restriction is also true for only outlines from this fonts
i.e. outlines exported into other font formats, for example TrueType or 
Type3.

This restriction is not intended to apply to connect time charges,
or flat rate connection/download fees for electronic bulletin board 
services.

--

Is that compatible with GPL 3?

Jason


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: pretty-printing in the notebook

[Jason Grout]

Jason Grout wrote:
> William Stein wrote:
>> On Jan 24, 2008 9:43 PM, Jason Grout <[EMAIL PROTECTED]> wrote:
>>> Following up on William's tip to look at the displayhook function, here
>>> is a function that will enable "pretty-printing" by default in the notebook:
>>>
>>> def pretty_print (object):
>>>  if object is None:
>>>  return
>>>  import __builtin__
>>>  __builtin__._=object
>>>  try:
>>>  print html("$"+latex(object)+"$")
>>>  except:
>>>  import sys
>>>  sys.__displayhook__(object)
>>>
>>> def notebook_pretty(enable=True):
>>>  import sys
>>>  if enable:
>>>  sys.displayhook = pretty_print
>>>  else:
>>>  sys.displayhook = sys.__displayhook__
>>>
>>> # To enable the pretty-printing
>>> notebook_pretty(True)
>>>
>>> Of course the function names could (and probably should) change.  This
>>> function makes the notebook much, much more user-friendly to new users,
>>> I think.  Where should this function be located?  Also, should it be a
>>> switch at the top of the notebook, like the evaluation drop-down menu?
>>>
>>> One problem with the above is that graphics objects are not shown by
>>> default (try doing plot(sin(x),1,2) after the above code).  Someone
>>> familiar with how graphic objects are shown by default now could
>>> probably trivially fix that problem, though (any takers?).
>>>
>> Sure.  This is like yours but slightly nicer and deals with graphics
>> nicely (and also lists of graphics objects):
>>
>> def pretty_print (object):
>> if object is None:
>> return
>> if isinstance(object, (sage.plot.plot.Graphics,
>> sage.plot.plot3d.base.Graphics3d)):
>> print repr(object)
>> return
>> import __builtin__
>> __builtin__._=object
>> try:
>> print html("$$"+latex(object)+"$$")
>> except:
>> import sys
>> sys.__displayhook__(object)
>>
>> def notebook_pretty(enable=True):
>> import sys
>> if enable:
>> sys.displayhook = pretty_print
>> else:
>> sys.displayhook = sys.__displayhook__
>>
>> # To enable the pretty-printing
>> notebook_pretty(True)
> 
> mhansen and mabshoff just pointed out on IRC that lprint() is the 
> existing function that is almost exactly this.  So I'm patching up 
> lprint instead.

A patch is up at #1922.  Could someone review it, please?


> 
> Can we make a very visible checkbox or button in the notebook interface 
> that toggles lprint?  I think it would be one thing that new users would 
> appreciate very, very much and also someone like me would appreciate 
> very much too.

This is trac #1923

Jason



--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Lulu publication

[Robert Bradshaw]

You can now by a hard copy of the Sage tutorial at http:// 
www.lulu.com/content/1932117

I will be publishing a DVD there too as soon as I can get the iso to  
upload.

- Robert


On Dec 28, 2007, at 1:06 PM, William Stein wrote:

> On Dec 27, 2007 5:58 AM, David Joyner <[EMAIL PROTECTED]> wrote:
>>
>> On Dec 27, 2007 3:40 AM, William Stein <[EMAIL PROTECTED]> wrote:
>>>
>>> Hi,
>>>
>>> I occasionally get emails like the one below.  There's no way I  
>>> have the
>>> time or inclination to burn and mail out DVD's of Sage to  
>>> people.  Does
>>> anybody:
>>>
>>>(1) want to volunteer to do this sort of thing in exchange for  
>>> some
>>>  "shipping and handling fees"; then all such requests get
>>>  refereed to you, or
>>>
>>>(2) Is there some dot-com that does something like this for a  
>>> fee?
>>
>>
>> Maybe lulu does:
>> http://www.lulu.com/en/help/disc_faq
>> Apparently, It has to be set up first and I don't know how easy it  
>> is to
>> upgrade to a new version.
>
> This looks excellent.   Basically you upload an iso of the data  
> dvd, and
> they burn and ship it on demand for < $10/copy.This is  
> perfect.  I could
> just do this once every time we have a major release.   I can add a  
> few
> dollars on each DVD, to pay whoever actually does the work of putting
> together the ISO, updating it, etc.
>
> David -- many thanks for tracking this down.
>
>  -- William
>
> 

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: infinity

[Robert Bradshaw]

I agree--rather than just having a signed/unsigned infinity ring, I  
think there should be an extended ring for Z, Q, R, C--both signed  
and unsigned when there is an absolute order. When does the concept  
of infinity make sense for a given ring? 1 (or 2)-point  
compactification? (not for Q), ordering (not for C), maybe an  
unbounded valuation (making "p-adic infinity" equal to zero?)

Implementation-wise, this could be accomplished via a generic wrapper  
around the rings and their elements (which I think could still be  
quite fast, and coercion would be natural and efficient too, not to  
mention the difficulties and inefficiencies raised by having multiple  
types for a single parent, or Integers with non-integer-ring parents).

The default sage oo would be +Infinity in Z \union {\pm \infty}.

On Jan 24, 2008, at 1:15 PM, David Roe wrote:

> So perhaps the solution to your problem is the extended integers  
> (or extended rationals).  This needs some work (both in terms of  
> speed and with having multiple types for elements of the same  
> parent), but it does have the benefit of returning 1 as the answer  
> to 1 + 0/infinity.  Perhaps the default sage infinity should be the  
> infinity of the extended integers, and there's a coercion map from  
> the extended integers to the extended rationals to the signed  
> infinity ring to the unsigned infinity ring, as well as coercions  
> from the integers to the extended integers and the rationals to the  
> extended rationals.
> David
>
> On Jan 24, 2008 12:48 PM, Burcin Erocal <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> Today I witnessed a mathematica user struggling with Sage because of
> the way Sage handles infinity. On trac #1915 you can see an example.
>
> On Thu, 17 Jan 2008 09:52:32 -0500
> David Harvey <[EMAIL PROTECTED]> wrote:
>
> > Question: why does the "unsigned infinity ring" not have a zero
> > element, whereas the "(signed) infinity ring" has a zero?
> >
> > This is okay:
> >
> > sage: 0 / Infinity
> > Zero
>
> I don't think this is okay. In this case we get
>
> sage: 1 + 0/Infinity
> A positive finite number
>
> If 0/Infinity is 0, the result of this should be 1.
>
> > But this is way confusing:
> >
> > sage: oo = UnsignedInfinityRing(Infinity)
> > sage: 0 / oo
> > A number less than infinity
> >
> > I totally expected the last output to be Zero. But it can't be,
> > because the UnsignedInfinityRing doesn't have a zero element.
>
> I would also expect the output to be zero. Moreover, there should be a
> way of returning a numeric zero from these operations. Otherwise the
> coercion model gets confused, and everything ends up being coerced  
> into
> "The Infinity Ring".
>
> sage: Infinity.parent()
> The Infinity Ring
>
>
> Thoughts?
>
> Burcin
>
>
> >


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Sage 2.10.1.alpha2 released!

[mabshoff]

Hello folks,

Not much happened since alpha1, but 25 tickets closed are enough
reason to do an alpha2 release. The notebook issue hasn't been
fixed yet and the ATLAS build improvements for Pentium M and
Athlon still aren't merged. Expect the next release to be a rc,
since we have closed close to 100 tickets and the release date
is approaching fast. I personally will concentrate on the 64 bit
OSX port (most of the spkgs I did touch in the last two days have
already been fixed), but in my eyes we need to fix the two huge
memleaks as well as the notebook issues before a release.

The review que is still full, so if you have some time please
review any of the tickets with patches listed in trac. A partial
list is appended to the end of this message. As usual please
report build failures and other issues.

The tarball [203MB] is available at

http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/sage-2.10.1.alpha2.tar

Cheers,

Michael

In Review:

Merged in alpha2:

#1028: Michael Abshoff: fix omega support for new valgrind
   release (3.3.0 once it is out)
#1050: Michael Abshoff: update optional valgrind.spkg to 3.3.0
   release
#1147: William Stein: change location of valgrind output files
   to something less obnoxious
#1550: Robert Miller: use libecm instead of pexpect+ecm binary
#1593: Martin Albrecht: m4ri -- the documentation of the echelon
   command only lists 1 algorithm but >= 2 algorithms are
   supported
#1617: William Stein: speed problem when factoring polynoms
#1623: Michael Abshoff: update gsl to 1.10
#1724: Craig Citro: Creating ModularForms from q-expansions
#1817: Martin Albrecht: crypto.mq.sr doctest coverage at 100%
#1818: Martin Albrecht: include AES polynomial system generator
   in reference manual
#1852: Michael Abshoff: Configure R to use Atlas, other build
   improvements to R package
#1869: Robert Miller: Implement show(list(graphs(n)))
#1873: Mike Hansen: elementary function expansion returns result
   in the wrong ring
#1889: Martin Albecht: 2.10.1.alpha2 doctest failure in
   crypto/mq/sr.py
#1890: Robert Miller: interfaces/libecm.pyx doctest failure
#1894: Martin Albrecht: toy_buchberger failures
#1895: Martin Albrecht: deal with passed through keyword arguments
   for Gröbner basis computation
#1898: Michael Abshoff, William Stein: numerical doctest failure
   for polynomial_element.pyx on Linux/Itanium
#1899: Robert Miller:  Making graphs with a matrix and loops=True
   blows up
#1900: Robert Miller, Jason Grout: Clean up adjacency matrix
   functions for graphs
#1905: Alex Ghitza: both E.Lseries and E.L_series are defined.
   Just define one of them, say E.Lseries.
#1906: Alex Ghitza: eisenstein_series_qexp does not pay attention
   to the field parameter
#1913: Burcin Erocal: poles of gamma
#1917: William Stein: get rid of crazy OS X charpoly workaround,
   since linbox isn't broken anymore
#1924: Robert Bradshaw, Clement Pernet: Optimize matrix multiply
   cache friendliness

Merged in alpha1:

#1166: William Stein: 2D terminal output is inconsistent and
   corrupted
#1217: Willem Jan Palenstijn: libfplll error codes
#1274: Martin Albrecht: modify singular interface to allow for
   verbose output
#1294: Mike Hansen: v.n() function blows up when v is a vector
#1306: Robert Miller: Bundles of graphs
#1418: Joel Mohler: magma element __floordiv__
#1508: William Stein: axes_label in plot() broken
#1577: Martin Albrecht: .coefficients() and .monomials() differ
   in order in multivariate polynomial rings
#1583: Craig Citro: simple modules of modular symbols over finite
   fields
#1604: William Stein: more locale problems with python exposed
   by matplotlib
#1606: William Stein: plotting -- add aspect_ratio option to show
   command
#1652: Mike Hansen: length of DAGs with loops calculation runs
   infinite
#1704: David Harvey: replace _DivPolyContext by _multiply_point
#1713: Martin Albrecht: fix SageElement._sage_
#1737: William Stein: ctl-c doesn't exit job in parametric_plot3d
#1718: William Stein: bug in parametric_plot
#1721: Josh Kantor, Michael Abshoff: Introduce SAGE_ATLAS_LIB to
   skip building of ATLAS
#1787: Michael Abshoff: Apply row-major GEMM major ATLAS errata
#1794: Willem Jan Palenstijn: Gram-Schmidt typo
#1804: Nick Alexander: Factorization.__mul__ assumes that the
   primes in the factorization commute, which may not be a
   valid assumption
#1812: Martin Albrecht: doctest coverage for finite_field_givaro up
   to 100%
#1814: Martin Albrecht: doctstrings for stream_cipher.py
#1820: Mike Hansen: update documentation for skew_partition.py
#1829: Martin Albrecht: small improvements for term ordering module
#1831: David Joyner: 3d docs: add more examples of parametric plots
#1832: Mike Hansen: change how real(...) is defined in Sage
#1833: William Stein: plot3d and parametric_plot3d can be very slow
   on some inputs
#1835: Martin Al

[sage-devel] Re: Sage 2.10.1.alpha2 released!

[William Stein]

On Jan 25, 2008 6:15 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> Not much happened since alpha1, but 25 tickets closed are enough
> reason to do an alpha2 release. The notebook issue hasn't been
> fixed yet and the ATLAS build improvements for Pentium M and
> Athlon still aren't merged. Expect the next release to be a rc,
> since we have closed close to 100 tickets and the release date
> is approaching fast. I personally will concentrate on the 64 bit
> OSX port (most of the spkgs I did touch in the last two days have
> already been fixed), but in my eyes we need to fix the two huge
> memleaks as well as the notebook issues before a release.

What notebook issues exactly are you talking about?
If you me GNUtls, the possibilities are (1) to not upgrade to the
latest version,
or (2) try to get pyopenssl to work with gnutls in ssh compat mode, or
(3) rebuild
the python-gnutls bindings to work with the newest version of gnutls (may or
may not work).

> The review que is still full, so if you have some time please
> review any of the tickets with patches listed in trac. A partial
> list is appended to the end of this message. As usual please
> report build failures and other issues.
>
> The tarball [203MB] is available at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/sage-2.10.1.alpha2.tar
>
> Cheers,
>
> Michael
>
> In Review:
>
> Merged in alpha2:
>
> #1028: Michael Abshoff: fix omega support for new valgrind
>release (3.3.0 once it is out)
> #1050: Michael Abshoff: update optional valgrind.spkg to 3.3.0
>release
> #1147: William Stein: change location of valgrind output files
>to something less obnoxious
> #1550: Robert Miller: use libecm instead of pexpect+ecm binary
> #1593: Martin Albrecht: m4ri -- the documentation of the echelon
>command only lists 1 algorithm but >= 2 algorithms are
>supported
> #1617: William Stein: speed problem when factoring polynoms
> #1623: Michael Abshoff: update gsl to 1.10
> #1724: Craig Citro: Creating ModularForms from q-expansions
> #1817: Martin Albrecht: crypto.mq.sr doctest coverage at 100%
> #1818: Martin Albrecht: include AES polynomial system generator
>in reference manual
> #1852: Michael Abshoff: Configure R to use Atlas, other build
>improvements to R package
> #1869: Robert Miller: Implement show(list(graphs(n)))
> #1873: Mike Hansen: elementary function expansion returns result
>in the wrong ring
> #1889: Martin Albecht: 2.10.1.alpha2 doctest failure in
>crypto/mq/sr.py
> #1890: Robert Miller: interfaces/libecm.pyx doctest failure
> #1894: Martin Albrecht: toy_buchberger failures
> #1895: Martin Albrecht: deal with passed through keyword arguments
>for Gröbner basis computation
> #1898: Michael Abshoff, William Stein: numerical doctest failure
>for polynomial_element.pyx on Linux/Itanium
> #1899: Robert Miller:  Making graphs with a matrix and loops=True
>blows up
> #1900: Robert Miller, Jason Grout: Clean up adjacency matrix
>functions for graphs
> #1905: Alex Ghitza: both E.Lseries and E.L_series are defined.
>Just define one of them, say E.Lseries.
> #1906: Alex Ghitza: eisenstein_series_qexp does not pay attention
>to the field parameter
> #1913: Burcin Erocal: poles of gamma
> #1917: William Stein: get rid of crazy OS X charpoly workaround,
>since linbox isn't broken anymore
> #1924: Robert Bradshaw, Clement Pernet: Optimize matrix multiply
>cache friendliness
>
> Merged in alpha1:
>
> #1166: William Stein: 2D terminal output is inconsistent and
>corrupted
> #1217: Willem Jan Palenstijn: libfplll error codes
> #1274: Martin Albrecht: modify singular interface to allow for
>verbose output
> #1294: Mike Hansen: v.n() function blows up when v is a vector
> #1306: Robert Miller: Bundles of graphs
> #1418: Joel Mohler: magma element __floordiv__
> #1508: William Stein: axes_label in plot() broken
> #1577: Martin Albrecht: .coefficients() and .monomials() differ
>in order in multivariate polynomial rings
> #1583: Craig Citro: simple modules of modular symbols over finite
>fields
> #1604: William Stein: more locale problems with python exposed
>by matplotlib
> #1606: William Stein: plotting -- add aspect_ratio option to show
>command
> #1652: Mike Hansen: length of DAGs with loops calculation runs
>infinite
> #1704: David Harvey: replace _DivPolyContext by _multiply_point
> #1713: Martin Albrecht: fix SageElement._sage_
> #1737: William Stein: ctl-c doesn't exit job in parametric_plot3d
> #1718: William Stein: bug in parametric_plot
> #1721: Josh Kantor, Michael Abshoff: Introduce SAGE_ATLAS_LIB to
>skip building of ATLAS
> #1787: Michael Abshoff: Apply row-major GEMM major ATLAS errata
> #1794: Willem Jan Palenstijn: Gram-Schmidt typo
> #1804: Nick Alexander: Factorization.__mul__ assumes that the
>primes in the fact

[sage-devel] Re: Sage 2.10.1.alpha2 released!

[mabshoff]

On Jan 26, 5:06 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Jan 25, 2008 6:15 PM, mabshoff
>
> <[EMAIL PROTECTED]> wrote:
>
> > Hello folks,
>
> > Not much happened since alpha1, but 25 tickets closed are enough
> > reason to do an alpha2 release. The notebook issue hasn't been
> > fixed yet and the ATLAS build improvements for Pentium M and
> > Athlon still aren't merged. Expect the next release to be a rc,
> > since we have closed close to 100 tickets and the release date
> > is approaching fast. I personally will concentrate on the 64 bit
> > OSX port (most of the spkgs I did touch in the last two days have
> > already been fixed), but in my eyes we need to fix the two huge
> > memleaks as well as the notebook issues before a release.
>
> What notebook issues exactly are you talking about?
> If you me GNUtls, the possibilities are (1) to not upgrade to the
> latest version,
> or (2) try to get pyopenssl to work with gnutls in ssh compat mode, or
> (3) rebuild
> the python-gnutls bindings to work with the newest version of gnutls (may or
> may not work).


Yes, that is the issue I was talking about. I would prefer (3) over
(2) over (1), but will be working on that problem later today.



Cheers,

Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Mark your calendars

[Nils Bruin]

*** Preliminary Announcement *

Sage days 9:

Mathematical graphics and visualization workshop

Vancouver, Canada
August 9 - 16, 2008

This instructional workshop is primarily aimed at graduate students in
mathematics and related areas. It will concentrate on  practical use
of
graphics in mathematical exposition, both in traditional and in new
media.

Tools covered will include the computer algebra system SAGE
(www.sagemath.org) and and the graphics description language
Postscript.

A large part of the program will consist of student projects, either
for
producing new and interesting mathematical graphics or for developing
graphics and visualization tools within SAGE.

Mark your calendars. Details on how to apply will follow soon.

Funded by MITACS / PIMS / SFU

**

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[dpvc]

> So to be crystal, are the files TeX-fonts-n.zip listed here
>
>    http://www.math.union.edu/~dpvc/jsMath/download/jsMath-fonts.html
>
> public domain?

Yes, that is how I understand it.  Certainly I am not planing to
restrict them in any way myself, and I am happy to give you special
permission to include them in sage if hat would help.

Davide
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[William Stein]

On Jan 25, 2008 2:43 PM, dpvc <[EMAIL PROTECTED]> wrote:
>
>
>
> > If I understand things correctly, the fonts up at 
> > http://www.math.union.edu/~dpvc/jsMath/download/jsMath-fonts.html are
> > based on the Bakoma fonts, and the license quoted above is the Bakoma
> > fonts license.  If you look at the "original Bakoma fonts" link at the
> > jsMath fonts page, you'll see inside the zip file a file named
> > BaKoMa-CM.Fonts, which contains the license agreement (and is quoted above).
>
> You are right that the original jsMath fonts were the BaKoMa fonts,
> but that is no longer the case.  The encoding used by the BaKoMa fonts
> turned out to be problematic, and so I made my own versions using
> mftrace directly from the Computer Modern metafont files.  So the
> BaKoMa copyright no longer applies.
>
> The Computer Modern fonts were put into the public domain by Knuth
> (see http://www.ntg.nl/maps/pdf/5_34.pdf), so I don't think there is
> any problem using these versions in Sage.

Hi Davide,

Thanks for your very helpful answer.

So to be crystal, are the files TeX-fonts-n.zip listed here

http://www.math.union.edu/~dpvc/jsMath/download/jsMath-fonts.html

public domain?

 -- William

>
> > 1. Davide does not distribute this license agreement (or any other) with
> > his modified versions of the Bakoma fonts.  Does that mean he claims the
> > copyright and he is the only one we need to work with for redistribution?
>
> No, I don't claim copyright.
>
> > 2. If the license agreement of the original Bakoma fonts is the one in
> > effect, then it sounds like we might have to work with them as well as
> > Davide to okay the redistribution of his modified fonts.
>
> No, BoKoMa is no longer involved, as these are unrelated to their
> versions of the fonts.
>
> Davide
>
> >
>



-- 
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: problem adding a function to a Sage class

[John Cremona]

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 sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: problem adding a function to a Sage class

[Mike Hansen]

> 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

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[root]

>Anyway, I would be most comfortable if we found out from the jsmath
>author (Davide Cervone, who I've cc'd and who sometimes reads sage-devel)
>whether it is ok with him if we distribute the jsmath fons with the
>sage distribution, even if said distribution could in some cases be sold
>(to support our project).

You might look into the Stix font project. 
Axiom uses the stix fonts in the firefox help browser.
Mathematica also allows their fonts to be used (but not
distributed with the system).

Tim


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[Jason Grout]

William Stein wrote:
> On Jan 25, 2008 12:14 AM, Jason Grout <[EMAIL PROTECTED]> wrote:
>> There has been some discussion about including the computer modern
>> jsMath fonts in Sage to ease installation.  The license agreement for
>> these fonts is:
>>
>> 
>> The author of this fonts grants to any individual or non-commercial
>> organization the right to use and to make an unlimited number of copies of
>> full package or selected fonts when this is done WITHOUT CHARGE
>> and has attached this file with licence agreement.
>>
>> This fonts cannot be sold or distributed with any commercial product or
>> used
>> in any commercial organization without additional agreement with author.
>> If you want to charge a small fee via distribution these fonts
>> or any derivations from this fonts, you should contact the author.
>>
>> This restriction is also true for only outlines from this fonts
>> i.e. outlines exported into other font formats, for example TrueType or
>> Type3.
>>
>> This restriction is not intended to apply to connect time charges,
>> or flat rate connection/download fees for electronic bulletin board
>> services.
>>
>> --
>>
>> Is that compatible with GPL 3?
> 
> No.  But I don't think it matters because these are fonts that will not
> be "binary linked" with Sage at runtime, so it isn't necessary that their
> copyright be compatible with the GPL.
> 
> That said, we need clarification regarding the statement
> "This fonts cannot be sold or distributed with any commercial product or
> used in any commercial organization without additional agreement with author.
> If you want to charge a small fee via distribution these fonts
> or any derivations from this fonts, you should contact the author."
> We need clarification, since we fully *do* intend to sell Sage.  E.g.,
> I sold a copy the other day in my office to a retired Boeing engineer
> for $20 (he wouldn't take no for an answer).And we'll likely also
> sell Sage online via lulo (as Robert Bradshaw mentioned).
> However, Sage is not-for-profit, so it's unclear whether it counts
> as "any commercial product".
> 
> Anyway, I would be most comfortable if we found out from the jsmath
> author (Davide Cervone, who I've cc'd and who sometimes reads sage-devel)
> whether it is ok with him if we distribute the jsmath fons with the
> sage distribution, even if said distribution could in some cases be sold
> (to support our project).


If I understand things correctly, the fonts up at 
http://www.math.union.edu/~dpvc/jsMath/download/jsMath-fonts.html are 
based on the Bakoma fonts, and the license quoted above is the Bakoma 
fonts license.  If you look at the "original Bakoma fonts" link at the 
jsMath fonts page, you'll see inside the zip file a file named 
BaKoMa-CM.Fonts, which contains the license agreement (and is quoted above).

1. Davide does not distribute this license agreement (or any other) with 
his modified versions of the Bakoma fonts.  Does that mean he claims the 
copyright and he is the only one we need to work with for redistribution?

2. If the license agreement of the original Bakoma fonts is the one in 
effect, then it sounds like we might have to work with them as well as 
Davide to okay the redistribution of his modified fonts.  According to 
the top of BaKoMa-CM.Fonts, the license holders are:

**
* 
  *
*BaKoMa Fonts Collection 
  *
*=== Level B === 
  *
* Version 1.1/12-Nov-94 
  *
* 
  *
*  Copyright (C) 1994, Basil K. Malyshev. All Rights Reserved. 
  *
* 
  *
**






and according to the bottom of the file, we can contact them at:





**
* Author location and bug report address 
  *
**

If you have some remarks about fonts shape quality, encoding or compatibily
with different software you can notify author:

  Basil K. Malyshev
  INSTITUTE FOR HIGH ENERGY PHYSICS
  IHEP, OMVT
  Moscow Region
  142284 PROTVINO
  RUSSIA

  E-Mail:   [EMAIL PROTECTED]
   or   [EMAIL PROTECTED]

Happy TeXing with my fonts.
Basil K. Malyshev, 12-Nov-1994, Geneva, Switzerland.

**
*End of BaKoMa-CM.Fonts file. 
  *
**


-Jason


--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.googl

[sage-devel] Re: Online free sage notebook slowness

[William Stein]

On Jan 23, 2008 11:02 PM, Ted Kosan <[EMAIL PROTECTED]> wrote:
>
> William wrote:
>
> > If anybody out there is a java expert, this might be a good problem to look 
> > at,
> > where this is "loading images many many times using sage's 3d plotting can
> > lead to problems".
>
> The problem might be related to how much memory is allocated to the
> Java plugin by default.  Here is some information about jmol and
> memory I found on the jmol wiki:
>
> http://wiki.jmol.org:81/index.php/Jmol_Applet#Giving_JmolApplet_more_memory_to_work_with
>

I tried upping the memory to 1GB but could still regularly crash
Firefox.  Safari
seemed to (still) work much better.  Maybe Firefox is just not so good...
Gmail crashes it a lot too.

William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[dpvc]

> If I understand things correctly, the fonts up at 
> http://www.math.union.edu/~dpvc/jsMath/download/jsMath-fonts.html are
> based on the Bakoma fonts, and the license quoted above is the Bakoma
> fonts license.  If you look at the "original Bakoma fonts" link at the
> jsMath fonts page, you'll see inside the zip file a file named
> BaKoMa-CM.Fonts, which contains the license agreement (and is quoted above).

You are right that the original jsMath fonts were the BaKoMa fonts,
but that is no longer the case.  The encoding used by the BaKoMa fonts
turned out to be problematic, and so I made my own versions using
mftrace directly from the Computer Modern metafont files.  So the
BaKoMa copyright no longer applies.

The Computer Modern fonts were put into the public domain by Knuth
(see http://www.ntg.nl/maps/pdf/5_34.pdf), so I don't think there is
any problem using these versions in Sage.

> 1. Davide does not distribute this license agreement (or any other) with
> his modified versions of the Bakoma fonts.  Does that mean he claims the
> copyright and he is the only one we need to work with for redistribution?

No, I don't claim copyright.

> 2. If the license agreement of the original Bakoma fonts is the one in
> effect, then it sounds like we might have to work with them as well as
> Davide to okay the redistribution of his modified fonts.

No, BoKoMa is no longer involved, as these are unrelated to their
versions of the fonts.

Davide
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[dpvc]

> You might look into the Stix font project. 
> Axiom uses the stix fonts in the firefox help browser.
> Mathematica also allows their fonts to be used (but not
> distributed with the system).

I do plan to support the STIX fonts in jsMath, but haven't had the
time to make the required data needed by jsMath for them yet.

Davide
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: infinity

[Burcin Erocal]

On Fri, 25 Jan 2008 05:32:44 -0800
"William Stein" <[EMAIL PROTECTED]> wrote:

> On Jan 25, 2008 3:36 AM, Robert Bradshaw
> <[EMAIL PROTECTED]> wrote:
> >
> > I agree--rather than just having a signed/unsigned infinity ring, I
> > think there should be an extended ring for Z, Q, R, C--both signed
> > and unsigned when there is an absolute order. When does the concept
> > of infinity make sense for a given ring? 1 (or 2)-point
> > compactification? (not for Q), ordering (not for C), maybe an
> > unbounded valuation (making "p-adic infinity" equal to zero?)
> >
> > Implementation-wise, this could be accomplished via a generic
> > wrapper around the rings and their elements (which I think could
> > still be quite fast, and coercion would be natural and efficient
> > too, not to mention the difficulties and inefficiencies raised by
> > having multiple types for a single parent, or Integers with
> > non-integer-ring parents).
> >
> > The default sage oo would be +Infinity in Z \union {\pm \infty}.
> >
> 
> Yes, this sounds good.
> 
> I -- then David Roe -- didn't implement something like the above I
> think only because we didn't need it for our applications (to modular
> symbols and p-adics).  But I could certainly see how it would
> be very useful for more general applications.

I think the current approach is good. It handles the corner cases where
infinity comes up efficiently. There is no need to keep track of
multiple types from the same parent, check every time arithmetic is
done, or to further complicate coercion.

The problem could be solved easily by returning 0 (a numeric zero) when
a finite value is divided by infinity. Then, the coercion model would
take over, and things would work again. 

i.e. with the proof of concept patch below, the following works

sage: t = UnsignedInfinityRing.gen()
sage: 1/t
0
sage: 1 + 0/t
1
sage: 1 + 1/t
1
sage: 1 + t
Infinity

Instead of implementing extended integers, rationals, reals or complex,
and complicating, as well as slowing down basic arithmetic, could we
just allow these infinity rings to behave not so algebraic? (and maybe
change their name and not call them a ring?)

Burcin


Here is the patch:

--- a/sage/rings/infinity.pyFri Jan 18 15:25:23 2008 -0800
+++ b/sage/rings/infinity.pyFri Jan 25 23:16:42 2008 +0100
@@ -263,7 +263,7 @@ class LessThanInfinity(RingElement):
 
 def _div_(self, other):
 if isinstance(other, UnsignedInfinity):
-return self
+return sage.rings.integer.Integer(0)
 raise TypeError, "quotient of oo by number < oo not defined"
 
 def __cmp__(self, other):

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: infinity

[William Stein]

On Jan 25, 2008 3:36 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>
> I agree--rather than just having a signed/unsigned infinity ring, I
> think there should be an extended ring for Z, Q, R, C--both signed
> and unsigned when there is an absolute order. When does the concept
> of infinity make sense for a given ring? 1 (or 2)-point
> compactification? (not for Q), ordering (not for C), maybe an
> unbounded valuation (making "p-adic infinity" equal to zero?)
>
> Implementation-wise, this could be accomplished via a generic wrapper
> around the rings and their elements (which I think could still be
> quite fast, and coercion would be natural and efficient too, not to
> mention the difficulties and inefficiencies raised by having multiple
> types for a single parent, or Integers with non-integer-ring parents).
>
> The default sage oo would be +Infinity in Z \union {\pm \infty}.
>

Yes, this sounds good.

I -- then David Roe -- didn't implement something like the above I
think only because we didn't need it for our applications (to modular
symbols and p-adics).  But I could certainly see how it would
be very useful for more general applications.

William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: jsMath fonts

[William Stein]

On Jan 25, 2008 12:14 AM, Jason Grout <[EMAIL PROTECTED]> wrote:
>
> There has been some discussion about including the computer modern
> jsMath fonts in Sage to ease installation.  The license agreement for
> these fonts is:
>
> 
> The author of this fonts grants to any individual or non-commercial
> organization the right to use and to make an unlimited number of copies of
> full package or selected fonts when this is done WITHOUT CHARGE
> and has attached this file with licence agreement.
>
> This fonts cannot be sold or distributed with any commercial product or
> used
> in any commercial organization without additional agreement with author.
> If you want to charge a small fee via distribution these fonts
> or any derivations from this fonts, you should contact the author.
>
> This restriction is also true for only outlines from this fonts
> i.e. outlines exported into other font formats, for example TrueType or
> Type3.
>
> This restriction is not intended to apply to connect time charges,
> or flat rate connection/download fees for electronic bulletin board
> services.
>
> --
>
> Is that compatible with GPL 3?

No.  But I don't think it matters because these are fonts that will not
be "binary linked" with Sage at runtime, so it isn't necessary that their
copyright be compatible with the GPL.

That said, we need clarification regarding the statement
"This fonts cannot be sold or distributed with any commercial product or
used in any commercial organization without additional agreement with author.
If you want to charge a small fee via distribution these fonts
or any derivations from this fonts, you should contact the author."
We need clarification, since we fully *do* intend to sell Sage.  E.g.,
I sold a copy the other day in my office to a retired Boeing engineer
for $20 (he wouldn't take no for an answer).And we'll likely also
sell Sage online via lulo (as Robert Bradshaw mentioned).
However, Sage is not-for-profit, so it's unclear whether it counts
as "any commercial product".

Anyway, I would be most comfortable if we found out from the jsmath
author (Davide Cervone, who I've cc'd and who sometimes reads sage-devel)
whether it is ok with him if we distribute the jsmath fons with the
sage distribution, even if said distribution could in some cases be sold
(to support our project).

 --William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: problem adding a function to a Sage class

[William Stein]

On Jan 25, 2008 8:30 AM, John Cremona <[EMAIL PROTECTED]> wrote:
>
> I'm sure this will have an instant simple answer.
>
> I have added a member function (method) called automorphisms(self) to
> an existing Sage class.  Namely, to the class  EllipticCurve_generic
> -- by inserting code into /sage/schemes/elliptic_curves/ell_generic.py
>
> I then do
>   sage -br
> and all seems well.
>
> But when I run Sage and create an instance of the class, it cannot see
> the new method:
>
> sage: E=EllipticCurve(0);E
> Elliptic Curve defined by y^2  = x^3 +1 over Rational Field
> sage: E.automorphisms()
> ---
> Traceback (most recent call last)
>
> /home/jec/sage/ in ()
>
> : 'EllipticCurve_rational_field'
> object has no attribute 'automorphisms'
>
> I'm sure that the code for automorphisms() is in the correct scope in the 
> file.
>
> Help!

That makes absolutely no sense, unless you're wrong
when you say:

> I then do
>   sage -br
> and all seems well.

above.  Could you modify ell_generic.py, then do "sage -br" again, and post
the exact output?

>
> John Cremona
>
> PS While I'm here, is there a way of doing "sage -br" without quitting
> Sage -- and losing all the variables etc that one has been testing
> with?

No.But you might find the save_session command useful, especially because
there is persistent history between sessions:

sage: a = 5
sage: e = EllipticCurve([1..5])
sage: save_session('foo')
sage:
Exiting SAGE (CPU time 0m0.12s, Wall time 0m27.67s).
teragon:vishigher was$ sage
--
| SAGE Version 2.10, Release Date: 2008-01-18|
| Type notebook() for the GUI, and license() for information.|
--

sage: load_session('foo')
sage: e
Elliptic Curve defined by y^2 + x*y + 3*y = x^3 + 2*x^2 + 4*x + 5 over
Rational Field



 -- William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] problem adding a function to a Sage class

[John Cremona]

I'm sure this will have an instant simple answer.

I have added a member function (method) called automorphisms(self) to
an existing Sage class.  Namely, to the class  EllipticCurve_generic
-- by inserting code into /sage/schemes/elliptic_curves/ell_generic.py

I then do
  sage -br
and all seems well.

But when I run Sage and create an instance of the class, it cannot see
the new method:

sage: E=EllipticCurve(0);E
Elliptic Curve defined by y^2  = x^3 +1 over Rational Field
sage: E.automorphisms()
---
Traceback (most recent call last)

/home/jec/sage/ in ()

: 'EllipticCurve_rational_field'
object has no attribute 'automorphisms'

I'm sure that the code for automorphisms() is in the correct scope in the file.

Help!

John Cremona

PS While I'm here, is there a way of doing "sage -br" without quitting
Sage -- and losing all the variables etc that one has been testing
with?

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: Lulu publication

[William Stein]

On Jan 25, 2008 1:35 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote:
>
> You can now by a hard copy of the Sage tutorial at http://
> www.lulu.com/content/1932117
>
> I will be publishing a DVD there too as soon as I can get the iso to
> upload.

Thanks.  I added a link here:
http://sagemath.org/documentation.html

William

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---

[sage-devel] Re: problem adding a function to a Sage class

[David Joyner]

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
>
>
> >
>

--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
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
-~--~~~~--~~--~--~---