[sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread 'Martin R' via sage-devel
The installation instructions say that ecl is roughly 3 times slower.  Once 
upon a time, when I was a fricas contributor, it made quite a difference. 
 But back than, sbcl was a no-go for sage (I forgot why).

I still love fricas' language.  I never underrstood why Python succeeded 
and Aldor didn't, once it became free.  But that's live.

Martin 

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread mmarco
Maybe one reason to prefer ecl is that it is embeddable, which could allow us 
to have a much faster interface than pexpect?

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread Emmanuel Charpentier
I'm not sure that fricas *has* to be a package : the current versins (6.4, 
6.5beta) already have the fricas interface compiled in :

/usr/local/sage-6.5/src/build/lib.linux-x86_64-2.7/sage/interfaces/fricas.py
/usr/local/sage-6.5/src/sage/interfaces/fricas.py
/usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.py
/usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.pyc

and fricas() calls a possible systemwide fricas. Successfully. Therefore 
fricas has the same Sage status as Mathematica, Magma or Matlab.

However, the fricas interface lacks a .fricas() method for getting the (a) 
fricas-palatable representation of some objects. It also lacks somethong to 
avid the ascii_art default output of fricas, which is quite unparsable by 
the sage() method (which exists).

I also saw somewhere on the list the suggestion of a algorithm=fricas 
option to integrate(), which seems a very good idea.

Nevertheless, having a fricas package which might replace a systemwide 
fricas installation might help its disemination.

HTH,

--
Emmanuel Charpentier

Le samedi 6 décembre 2014 18:23:32 UTC+1, vdelecroix a écrit :

 Hello,

 I just discover FriCAS and its tremendous possibilities. I just updated 
 the package that we ship we Sage from version 0.3.1 to version 1.2.4 (more 
 information at http://trac.sagemath.org/ticket/9465). It might become a 
 more standard package.

 I have a very naive question: the version of lisp we have in Sage is ecl, 
 does it make a huge difference with sbcl ?

 Best
 Vincent


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread Emmanuel Charpentier


Le samedi 6 décembre 2014 19:01:46 UTC+1, Emmanuel Charpentier a écrit :

 I'm not sure that fricas *has* to be a package : the current versins (6.4, 
 6.5beta) already have the fricas interface compiled in :


 /usr/local/sage-6.5/src/build/lib.linux-x86_64-2.7/sage/interfaces/fricas.py
 /usr/local/sage-6.5/src/sage/interfaces/fricas.py

 /usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.py

 /usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.pyc

 and fricas() calls a possible systemwide fricas. Successfully. Therefore 
 fricas has the same Sage status as Mathematica, Magma or Matlab.

 However, the fricas interface lacks a .fricas() method for getting the (a) 
 fricas-palatable representation of some objects. It also lacks somethong to 
 avid the ascii_art default output of fricas, which is quite unparsable by 
 the sage() method (which exists).

 I also saw somewhere on the list the suggestion of a algorithm=fricas 
 option to integrate(), which seems a very good idea.

 Nevertheless, having a fricas package which might replace a systemwide 
 fricas installation might help its disemination.

 HTH,

 --
 Emmanuel Charpentier

 Le samedi 6 décembre 2014 18:23:32 UTC+1, vdelecroix a écrit :

 Hello,

 I just discover FriCAS and its tremendous possibilities. I just updated 
 the package that we ship we Sage from version 0.3.1 to version 1.2.4 (more 
 information at http://trac.sagemath.org/ticket/9465). It might become a 
 more standard package.

 I have a very naive question: the version of lisp we have in Sage is ecl, 
 does it make a huge difference with sbcl ?

 Best
 Vincent


Ahem. I have to retract that : if we want to add an 'algorithm=fricas'  
option to sage's integrate(), fricas just *has* to be there as a standard 
package.

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread William Stein
On Sat, Dec 6, 2014 at 11:13 AM, Emmanuel Charpentier
emanuel.charpent...@gmail.com wrote:


 Le samedi 6 décembre 2014 19:01:46 UTC+1, Emmanuel Charpentier a écrit :

 I'm not sure that fricas *has* to be a package : the current versins (6.4,
 6.5beta) already have the fricas interface compiled in :


 /usr/local/sage-6.5/src/build/lib.linux-x86_64-2.7/sage/interfaces/fricas.py
 /usr/local/sage-6.5/src/sage/interfaces/fricas.py

 /usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.py

 /usr/local/sage-6.5/local/lib/python2.7/site-packages/sage/interfaces/fricas.pyc

 and fricas() calls a possible systemwide fricas. Successfully. Therefore
 fricas has the same Sage status as Mathematica, Magma or Matlab.

 However, the fricas interface lacks a .fricas() method for getting the (a)
 fricas-palatable representation of some objects. It also lacks somethong to
 avid the ascii_art default output of fricas, which is quite unparsable by
 the sage() method (which exists).

 I also saw somewhere on the list the suggestion of a algorithm=fricas
 option to integrate(), which seems a very good idea.

 Nevertheless, having a fricas package which might replace a systemwide
 fricas installation might help its disemination.

 HTH,

 --
 Emmanuel Charpentier

 Le samedi 6 décembre 2014 18:23:32 UTC+1, vdelecroix a écrit :

 Hello,

 I just discover FriCAS and its tremendous possibilities. I just updated
 the package that we ship we Sage from version 0.3.1 to version 1.2.4 (more
 information at http://trac.sagemath.org/ticket/9465). It might become a more
 standard package.

 I have a very naive question: the version of lisp we have in Sage is ecl,
 does it make a huge difference with sbcl ?

 Best
 Vincent


 Ahem. I have to retract that : if we want to add an 'algorithm=fricas'
 option to sage's integrate(), fricas just *has* to be there as a standard
 package.

No, your original statement was correct, since  we have
algorithm='magma' for some functions.

William


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

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread Nils Bruin
On Saturday, December 6, 2014 11:13:27 AM UTC-8, Emmanuel Charpentier wrote:

Ahem. I have to retract that : if we want to add an 'algorithm=fricas'  
 option to sage's integrate(), fricas just *has* to be there as a standard 
 package.


There is precedent otherwise. For instance NumberField(x^5+4).galois_group 
has an option algorithm=magma. Magma can compute galois groups of a much 
larger class of number fields than the other options can, and magma is 
(naturally) not a standard package. 

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.


[sage-devel] Re: fricas pkg in Sage

2014-12-06 Thread John H Palmieri


On Saturday, December 6, 2014 9:33:57 AM UTC-8, Martin R wrote:

 The installation instructions say that ecl is roughly 3 times slower. 
  Once upon a time, when I was a fricas contributor, it made quite a 
 difference.  But back than, sbcl was a no-go for sage (I forgot why).


I think it was because to build sbcl from source, you needed (and still 
need) an ANSI-compliant Common Lisp already on your machine. So we would 
maybe need to ship two lisps, sbcl plus another one to build sbcl.

-- 
John

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.