On Jan 4, 2008 2:31 PM, Jaap Spies <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just tried to mimic the mlab session at:
> http://gael-varoquaux.info/blog/?p=3
>
> With some tricks you can do this in sage, if you have the experimental
> ETS installed :)
>
> [EMAIL PROTECTED] sage-2.8.15]$ ./sage -sh
> S
Hi,
2.9.2.rc1 is very close to the final release. The only changes that
will still go in are 3D plotting fixes and anything critical that
turns up and is simple enough to be refereed. 2.9.2 should happen
by midnight tonight (PST).
The tarball [198MB] is at
http://sage.math.washington.edu/home
Hi,
I'm going to separate the issues here--multiplication and addition.
The former is easily handled by implementing the coercion ZZ ->
BooleanMonomials via Z/2Z. David Roe and I still need to finish
pushing the new coercion model through, but I've been sidetracked
doing 3d and other stuf
Hi,
While browsing the
http://sage.math.washington.edu/home/wdj/teaching/index.html
(btw which is the best tutorial for sage I ever found), I was looking at this
http://sage.math.washington.edu/home/wdj/teaching/granville-calculus/granville-calculus.pdf
page 75. compare figure 5.9 (original h
and what about the (linux2,gfortran) pair that I tried to force and
that still does not seem to be accepted?
best,
Johann
On Jan 4, 2:57 pm, Joshua Kantor <[EMAIL PROTECTED]> wrote:
> Well, that still doesn't explain anythinig as I get the same output
> for sys.platform and sys.name.
>
> Neverthe
strange... I just tried in the cluster of machines at work, where I
have a different shell environment, and have access to RHEL3 and 4
machines, and they all result in os.name returning posix and
sys.platform returning linux2
I will try your spkg today if I have still time, or tomorrow.
best,
Well, that still doesn't explain anythinig as I get the same output
for sys.platform and sys.name.
Nevertheless, I may know how to fix your problem even though I don't
know why its happening.
Try to put this spkg
http://sage.math.washington.edu/home/jkantor/spkgs/numpy-20071120-1.0.3.1.p3.spkg
hi Josh, here it is :
Sage subshell$ pwd
/data1/sources/sage-2.9.1.1/spkg/build/numpy-20071020-1.0.3.1.p3/src
Sage subshell$ cd ../../../../
Sage subshell$ ls
COPYING.txt data example.sage install.log ipython local
makefile matplotlibrc README.txt sage sage-2.9.1.txt sage-python
spkg t
some more debugging : I put printouts to 2 calls in fcompiler/
__init__.py, at the beginning of new_fcompiler and
_find_existing_fcomplers. The full screen output is copied below.
Several comments :
1) these methods seem to be called several times, not always with the
same arguments. In order :
CA
some more debugging : I put printouts to 2 calls in fcompiler/
__init__.py, at the beginning of new_fcompiler and
_find_existing_fcomplers. The full screen output is copied below.
Several comments :
1) these methods seem to be called several times, not always with the
same arguments. In order :
CA
Robert wrote:
> > Do you think it is okay to manually edit the various build scripts to
> > make them build as desired and then just record what was edited in the
> > SPKG.txt file?
>
> The route we have traditionally gone down is to place patch files in
> a "patches" directory and then apply the
Another thought. Please go into sage-2.9*/local/bin and
do
./python
to start the local python
what does
import sys
sys.platform
output.
(it should be something like linux2, but I wonder if it might come out
posix for you)
Josh
On Jan 4, 1:22 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> w
ok, I am doing a little debugging : the numpy error message comes from
numpy/distutils/fcompiler/__init__.py in the new_fcompiler function.
This function seems to be called with plat=None and compiler=gfortran.
As plat=None, the first thing that this method function does is
plat=os.name I chec
On Jan 4, 10:14 pm, Johannct <[EMAIL PROTECTED]> wrote:
Hi,
> hello,
> having root priviledge I went ahead and did : ln -s /usr/lib/
> libgfortran.so.1 /usr/lib/libgfortran.so
> It fixes the problem in the sense that I am now back to square one,
> with the initial numpy build failure :
Ok, but
hello,
having root priviledge I went ahead and did : ln -s /usr/lib/
libgfortran.so.1 /usr/lib/libgfortran.so
It fixes the problem in the sense that I am now back to square one,
with the initial numpy build failure :
running install
running build
running config_cc
unifing config_cc, config, build
On Jan 4, 9:52 pm, Johannct <[EMAIL PROTECTED]> wrote:
> fresh rebuild from a vanilla source, LD_LIBRARY_PATH, PYTHONPATH
> etc... unsetenved, and using make and *not* make -j2 and using
> SAGE_FORTRAN set to gfortran, I still stumble :
>
> make[3]: `libcblas.so' is up to date.
> make[3]: Leavin
mabshoff wrote:
> Hi Jaap,
>
> Apply the patch at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.9.2/rc1/7937.patch
>
> and it will be fixed.
>
Yes, fixed!
Jaap
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@google
Yes, this is exactly as expected. Thanks!
On Jan 4, 2008 1:01 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hi Jaap,
>
> > On Fedora 7, after applying both patches
> >
> > I saw this:
> >
> > sage -t devel/sage-main/sage/plot/plot3d/base.pyx (skipping) --
> > nodoctest.py file in directory
> >
On Jan 4, 2008 12:58 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
>
> On Jan 4, 9:52 pm, Johannct <[EMAIL PROTECTED]> wrote:
> > fresh rebuild from a vanilla source, LD_LIBRARY_PATH, PYTHONPATH
> > etc... unsetenved, and using make and *not* make -j2 and using
> > SAGE_FORTRAN set to gfortran, I
fresh rebuild from a vanilla source, LD_LIBRARY_PATH, PYTHONPATH
etc... unsetenved, and using make and *not* make -j2 and using
SAGE_FORTRAN set to gfortran, I still stumble :
make[3]: `libcblas.so' is up to date.
make[3]: Leaving directory `/data1/sources/sage-2.9.1.1/spkg/build/
atlas-3.8.p6/AT
Hi Jaap,
> On Fedora 7, after applying both patches
>
> I saw this:
>
> sage -t devel/sage-main/sage/plot/plot3d/base.pyx (skipping) -- nodoctest.py
> file in directory
> sage -t devel/sage-main/sage/plot/plot3d/point_c.pxi (skipping) --
> nodoctest.py file in directory
> sage -t devel/sage-
William Stein wrote:
> On Jan 4, 2008 10:18 AM, mabshoff
> <[EMAIL PROTECTED]> wrote:
>>
>>
>> On Jan 4, 7:01 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>>> On Jan 4, 2008 9:58 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>>
>>
The following tests failed:
sage -t devel/sage-m
mabshoff wrote:
>>> I just merged #1672 into my rc1 build on sage.math and the plot3d
>>> examples still have failures. You wrote me initially that you turned
>>> of doctesting for those files, but it looks like that didn't make it
>>> into the patch.
>> Oops, hg and empty files. Anyways, I've po
> > I just merged #1672 into my rc1 build on sage.math and the plot3d
> > examples still have failures. You wrote me initially that you turned
> > of doctesting for those files, but it looks like that didn't make it
> > into the patch.
>
> Oops, hg and empty files. Anyways, I've posted a second p
I rebuilt in place, and I just realized that I might have issued the
command make -j2 the first time, as I have a dual core machine. So I
am just remaking with this command just to see. If that fails I
will start from a fresh source again.
On Jan 4, 11:18 am, mabshoff <[EMAIL PROTECTED]
On Jan 4, 8:10 pm, Johannct <[EMAIL PROTECTED]> wrote:
> ok, now it fails before numpy seemingly : it did not build all the
> atlas librairies and bail out after complainng that it cannot cp
> them... I relaunched a make, and it seems to build all the libs again,
> which is strange...
> Anyway :
On Jan 4, 2008, at 9:39 AM, Ted Kosan wrote:
> Robert,
>
> Do you think it is okay to manually edit the various build scripts to
> make them build as desired and then just record what was edited in the
> SPKG.txt file?
The route we have traditionally gone down is to place patch files in
a "pat
ok, now it fails before numpy seemingly : it did not build all the
atlas librairies and bail out after complainng that it cannot cp
them... I relaunched a make, and it seems to build all the libs again,
which is strange...
Anyway :
cp /data1/sources/sage-2.9.1.1/spkg/build/atlas-3.8.p6/ATLAS-build
On Jan 4, 2008 10:18 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Jan 4, 7:01 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > On Jan 4, 2008 9:58 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
>
>
> >
> > > The following tests failed:
> >
> > > sage -t
> > > devel/sage-main/sage/
On Jan 4, 7:01 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Jan 4, 2008 9:58 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> > The following tests failed:
>
> > sage -t devel/sage-main/sage/schemes/elliptic_curves/ell_point.py
> > sage -t
> > devel/sage-main/sage/sch
On Jan 4, 2008 9:58 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> mabshoff wrote:
> > Hi,
> >
> > We are still being very conservative and only merge a couple
> > more patches. We also updated the new 3D plotting code that Robert
> > Bradshaw and William Stein wrote.
> >
> > The tarball [197MB] is
mabshoff wrote:
> Hi,
>
> We are still being very conservative and only merge a couple
> more patches. We also updated the new 3D plotting code that Robert
> Bradshaw and William Stein wrote.
>
> The tarball [197MB] is at
>
> http://sage.math.washington.edu/home/mabshoff/sage-2.9.2.rc0.tar
>
On Jan 4, 2008 9:40 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We are still being very conservative and only merge a couple
> more patches. We also updated the new 3D plotting code that Robert
> Bradshaw and William Stein wrote.
>
> The tarball [197MB] is at
>
> http://sage.math.washing
On Jan 4, 2008 9:39 AM, Ted Kosan <[EMAIL PROTECTED]> wrote:
>
> Robert,
>
> Do you think it is okay to manually edit the various build scripts to
> make them build as desired and then just record what was edited in the
> SPKG.txt file?
>
> Also, how much software can we require the user have pre-
Hi,
We are still being very conservative and only merge a couple
more patches. We also updated the new 3D plotting code that Robert
Bradshaw and William Stein wrote.
The tarball [197MB] is at
http://sage.math.washington.edu/home/mabshoff/sage-2.9.2.rc0.tar
Please build test this and report a
Robert,
Do you think it is okay to manually edit the various build scripts to
make them build as desired and then just record what was edited in the
SPKG.txt file?
Also, how much software can we require the user have pre-installed on
their system before building jmol-src.spkg? At this point we
On Jan 4, 6:18 pm, Johannct <[EMAIL PROTECTED]> wrote:
Hi Johann,
> hi Josh,
> unsetting the env vars did not change anything seemingly. So I am now
> pointing to gfortran the way you described and I am rebuilding
> everything (id est I just made a make distclean).
Good.
> BTW, I build LPAAC
hi Josh,
unsetting the env vars did not change anything seemingly. So I am now
pointing to gfortran the way you described and I am rebuilding
everything (id est I just made a make distclean).
BTW, I build LPAACK and ATLAS on my own for scipy recently, and it was
absolutely critical to set my dual
On Jan 4, 2008 12:57 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Jan 4, 12:50 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> > On Jan 4, 2008 10:01 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> > > On Jan 3, 2008 12:13 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > > > Hi
On Jan 4, 12:55 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
Hi John,
> I have put an updated eclib
> athttp://www.warwick.ac.uk/staff/J.E.Cremona/eclib-20071231.p1.spkg
>
> This version, which builds on mabshoff's eclib-20071231.p0.spkg,
> handles the interface with NTL's ZZ_p class better
On Jan 4, 12:50 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> On Jan 4, 2008 10:01 AM, William Stein <[EMAIL PROTECTED]> wrote:
Hi,
> > On Jan 3, 2008 12:13 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > I posted my thoughts on the curent status and the future of Sage.calc
I have put an updated eclib at
http://www.warwick.ac.uk/staff/J.E.Cremona/eclib-20071231.p1.spkg
This version, which builds on mabshoff's eclib-20071231.p0.spkg,
handles the interface with NTL's ZZ_p class better (using a cached
list of ZZ_pContext's for those who know NTL) which should certailny
On Jan 4, 2008 10:01 AM, William Stein <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 3, 2008 12:13 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I posted my thoughts on the curent status and the future of Sage.calculus
> > here:
> >
> > http://planet.sagemath.org/
> >
> > direct link
On Fri, 4 Jan 2008 10:52:38 +0100
"Fabio Tonti" <[EMAIL PROTECTED]> wrote:
> Well, yes I most definitely would, since I don't always have my
> Laptop with me and also work on non-Unix machines (unfortunatly).
> So I think its feasible to have a "live"-option around. But maybe the
> effort to crea
Hi,
I got this email from Peter Doyle and with his permission I am
forwarding it here.
-- Forwarded message --
From: Peter Doyle <>
Date: Jan 4, 2008 12:28 AM
Subject: sage.calculus
To: Ondrej Certik <>
Hi Ondrej,
I like the idea of moving sage.calculus over to SymPy, hopeful
We modify numpy so that it is supposed to use sage_fortran, which
wraps either the g95 fortran we include
or a fortran compiler the user specifies. The point of this is to
avoid problems with the user having
multiply incompatible fortran compilers (since there are a bunch)
Unfortunately somethin
Well, yes I most definitely would, since I don't always have my Laptop with
me and also work on non-Unix machines (unfortunatly).
So I think its feasible to have a "live"-option around. But maybe the effort
to create one should just be postponed?
Now there's another thing which comes to my mind: Wo
On Jan 3, 2008 1:46 AM, Fabio Tonti <[EMAIL PROTECTED]> wrote:
> It's a very good idea for demonstrations... Imagine having sage on a
> USB-drive an booting it directly
Would _you_ actually use it. So far in this thread only one
person -- Tim Daly -- has said they would actually use a live
C
On Jan 4, 2008 12:56 AM, Fabio Tonti <[EMAIL PROTECTED]> wrote:
> The page numbers are numbers in the pdf version (in parentheses the printed
> page numbers)
> I'm actually not sure about how to reference the page numbers...
>
> page 175 (162): ** instead of ^;
> the pyx example says: "sage: y(x)
On Jan 3, 2008 12:13 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I posted my thoughts on the curent status and the future of Sage.calculus
> here:
>
> http://planet.sagemath.org/
>
> direct link is:
>
> http://ondrejcertik.blogspot.com/2008/01/sympysympycore-pure-python-up-to-5x.html
The page numbers are numbers in the pdf version (in parentheses the printed
page numbers)
I'm actually not sure about how to reference the page numbers...
page 175 (162): ** instead of ^;
the pyx example says: "sage: y(x) = x*sin(x**2)"
using the "**" is nice for python, but isn't Sage emphasizing
On Jan 4, 2008 12:26 AM, Fabio Tonti <[EMAIL PROTECTED]> wrote:
> Where should I complain about typos in the documentation?
Send an email to sage-devel listing all typos you find. We'll
open a trac ticket with them.
> (or should I at all?)
Sage is free software, and you "pay" for it by helping
On Jan 4, 2008, at 12:26 AM, Fabio Tonti wrote:
> Where should I complain about typos in the documentation? (or
> should I at all?)
Yes, please do. The optimal place to complain is on the bugtracer
http://sagetrac.org/sage_trac/
There's even a category for "documentation." If you can provid
Where should I complain about typos in the documentation? (or should I at
all?)
Another question: will there also be a presentation about Sage at the San
Diego AMS meeting?
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To un
On Jan 3, 2008 1:56 PM, DuaneKaufman <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Thanks for the pointer, that makes reporting things _much_ simpler.
>
> With regard to my earlier problem with scipy not installing, I
> eventually removed the spkg, and re-upgraded, and things went OK.
>
> ???
That sugge
55 matches
Mail list logo
