purple

7 views
Skip to first unread message

William Stein

unread,
Sep 2, 2010, 4:23:25 AM9/2/10
to ps...@googlegroups.com
Hi,

I added another page about "goals and general strategy" here:

http://purple.sagemath.org/goals.html

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

Bill Hart

unread,
Sep 2, 2010, 7:41:32 AM9/2/10
to ps...@googlegroups.com
This looks like a sensible list of things to do. Getting rid of pexpect. Yay!

But what's this, no Lisp!! What about the hoard of Lisp developers we
have standing by who want to help with all sorts of number theoretical
stuff!!

Bill.

Bill Hart

unread,
Sep 2, 2010, 9:28:23 AM9/2/10
to ps...@googlegroups.com
I updated the Windows port page to reflect the cuts psage makes (which
makes a full MSVC Windows port look more feasible).

Of the 35 essential packages, 17 have 64 bit Windows support already.
A number of the remaining packages are pure C and shouldn't be
difficult ports.

Could someone explain to me what SQLalchemy, sage_scripts and termcap
do in Sage, and whether they are needed for psage.

It looks like Singular is now probably the hardest port to Windows,
along with termcap.

Bill.

P.S: I realise that porting psage to Windows is not one of the
*primary* objectives of having psage. But we may as well take
advantage of the opportunity it presents.

Bill Hart

unread,
Sep 2, 2010, 10:35:58 AM9/2/10
to ps...@googlegroups.com
Actually, some of the packages further down the page are also
required. I moved some up. I guess we also definitely need numpy,
sympy and mpmath?

Here is the page:

http://wiki.sagemath.org/windows/general-package-analysis#preview

Corrections welcome. A lot of the information on that page was/is just
plain wrong.

Bill.

Reply all
Reply to author
Forward
0 new messages