Dan Drake wrote:
> I think I would be very happy if I wrote my book and someone else wanted
> to include a version of one of the chapters into their own work, even if
> that work otherwise used ordinary copyright, and if readers of the new
> book didn't have access to "Transparent" copies, or if
Here is mine :
gcc version 4.3.2 20081105 (Red Hat 4.3.2-7) (GCC)
Nathann
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.c
On Mon, 04 Jan 2010 at 12:43AM +0800, Tim Joseph Dumol wrote:
> Changes to the notebook should be made to the sagenb spkg found at
> http://nb.sagemath.org, and updated to the latest version at the
> repository (hg pull http://sage.math.washington.edu:8100). Development
> on the notebook should be
Okay, I'm late to this party, but I'm very interested in this issue, as
I have plans to write a book that would be licensed under something like
GFDL or CC by-sa.
On Tue, 29 Dec 2009 at 10:24PM -0700, Jason Grout wrote:
> So it still seems that GFDL has some sort of requirement about
> distributin
On Mon, 04 Jan 2010 at 06:38PM -0800, John H Palmieri wrote:
> > The new polybori spkg is over three times as large as the previous one!
> > Does anyone know why? I see that the source got updated, but why did it,
> > in two months, triple in size?
>
> Unpacked, the two aren't that different in si
Well, this is basically a clone of mathematicas "SphericalPlot3d" only
that i thought the 3d was redundant.
I've published the function here: http://www.sagenb.org/pub/1319/ .
And cloned the examles in
http://reference.wolfram.com/mathematica/ref/SphericalPlot3D.html
So there. This would be my fi
On Jan 5, 4:21 am, William Stein wrote:
> Hi,
>
> Does anybody reading this message use gfan in Sage? Maybe gfan
> shouldn't be included in Sage. I would be OK with removing it if
> there isn't any support for it. That it never gets updated is
> suggestive.
>
> William
>
>
Doing a search o
Hi,
Does anybody reading this message use gfan in Sage? Maybe gfan
shouldn't be included in Sage. I would be OK with removing it if
there isn't any support for it. That it never gets updated is
suggestive.
William
On Mon, Jan 4, 2010 at 7:47 PM, Dr. David Kirkby
wrote:
> I note that gfan h
I note that gfan hard-codes the compiler names gcc/g++. Trying to fix that, I
soon discovered the Sun compiler thinks there is an error in the code, with
something supposed to return a value, but not doing so.
gfan-0.3.p6/patches/
gfan-0.3.p6/patches/Makefile
Finished extraction
On 01/04/2010 11:11 AM, Jaap Spies wrote:
> sage -t "devel/sage/sage/misc/sagedoc.py"
> **
> File "/home/jaap/downloads/sage-4.3/devel/sage/sage/misc/sagedoc.py", line
> 897:
> sage: browse_sage_doc(identity_matrix, 'html',
On Jan 4, 5:30 pm, Dan Drake wrote:
> On Mon, 04 Jan 2010 at 03:06PM -0800, John H Palmieri wrote:
> > > > sage/rings/polynomial/pbori.cpp: In function ‘PyObject*
> > > > __pyx_pf_4sage_5rings_10polynomial_5pbori_easy_linear_factors(PyObject*,
> > > > PyObject*)’:
> > > > sage/rings/polynomial
Dr. David Kirkby wrote:
> If anyone has a spare minute, here's something that must be about as simple
> as
> they come to review. The additional code is all on one line.
>
> http://trac.sagemath.org/sage_trac/ticket/7067
>
> cddlib fails to build with the Sun compiler, complaining:
>
> Undefin
If anyone has a spare minute, here's something that must be about as simple as
they come to review. The additional code is all on one line.
http://trac.sagemath.org/sage_trac/ticket/7067
cddlib fails to build with the Sun compiler, complaining:
Undefined first referenced
Dan Drake wrote:
>
> The new polybori spkg is over three times as large as the previous one!
> Does anyone know why? I see that the source got updated, but why did it,
> in two months, triple in size?
>
> Dan
>
The ticket's title is:
#7271: "some small polybori interface fixes"
so it does see
On Mon, 04 Jan 2010 at 03:06PM -0800, John H Palmieri wrote:
> > > sage/rings/polynomial/pbori.cpp: In function ‘PyObject*
> > > __pyx_pf_4sage_5rings_10polynomial_5pbori_easy_linear_factors(PyObject*,
> > > PyObject*)’:
> > > sage/rings/polynomial/pbori.cpp:38652: error: ‘easy_linear_factors’ wa
Jaap Spies wrote:
> Dr. David Kirkby wrote:
>
>> I'll fix the atlas package now. I don't guarantee it will build, but I'll fix
>> this ctypes issue, by putting something a bit more portable. That will
>> hopefully
>> report the system as 64-bit and not leave a blank, which is possibly what
>> scr
Dr. David Kirkby wrote:
> I'll fix the atlas package now. I don't guarantee it will build, but I'll fix
> this ctypes issue, by putting something a bit more portable. That will
> hopefully
> report the system as 64-bit and not leave a blank, which is possibly what
> screwing atlas up.
>
Hope so!
Jaap Spies wrote:
> Jaap Spies wrote:
>> Jaap Spies wrote:
>
>
> next report
>
> j...@opensolaris:~/Downloads/sage-4.3.1.alpha0$ ls spkg/installed
> blas-20070724 gnutls-2.2.1.p5
> pyprocessing-0.52.p0
> boehm_gc-7.1.p2 graphs-20070722.p1
Jaap Spies wrote:
> Jaap Spies wrote:
next report
j...@opensolaris:~/Downloads/sage-4.3.1.alpha0$ ls spkg/installed
blas-20070724 gnutls-2.2.1.p5
pyprocessing-0.52.p0
boehm_gc-7.1.p2 graphs-20070722.p1python-2.6.2.p4
boost-cropped-1.34
On Mon, 4 Jan 2010 15:06:57 -0800 (PST), John H Palmieri
wrote:
> > > My build on Fedora 12 intel i7 860 64 bit failed on
> >
> > > gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall
> > > -Wstrict-prototypes -fPIC
> > > -I/home/jaap/downloads/sage-4.3.1.alpha0/local/include/cudd
> > > -I/h
In common lisp (part of Maxima) one can do this:
(integer-decode-float (exp 1.0d0))
which produces 3 values:
6121026514868073
-51
1
In maxima you would have to prefix this with :lisp.
In Sage, perhaps
maxima ":lisp (integer-decode-float "
Though how Sage treats multiple-value retur
I've had problems building mpir in Sage, so downloaded the clean source, to try
it outside. The setup is
Sun Ultra 27 - quad core 3.333 GHz Xeon. 12 GB RAM
Open Solaris 06/2009
Sun Studio 12.1
First, the good news.
1) Configuring like this works
$ export CC=/opt/sunstudio12.1/bin/cc
$ export C
On Jan 4, 6:48 am, John Cremona wrote:
> 2010/1/4 Jaap Spies :
>
>
> > My build on Fedora 12 intel i7 860 64 bit failed on
>
> > gcc -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes
> > -fPIC -I/home/jaap/downloads/sage-4.3.1.alpha0/local/include/cudd
> > -I/home/jaap/downlo
Dr. David Kirkby wrote:
> Jaap Spies wrote:
>> David Kirkby wrote:
>>> The following gives a rough idea of what works on Open Solaris on a
>>> Sun Ultra 27. ( I say 'rough' as some packages I modified, and some
>>> may not be working as they should).
>>>
>>> Hardware: Sun Ultra 27, 12 GB RAM, quad
Jaap Spies wrote:
> David Kirkby wrote:
>> The following gives a rough idea of what works on Open Solaris on a
>> Sun Ultra 27. ( I say 'rough' as some packages I modified, and some
>> may not be working as they should).
>>
>> Hardware: Sun Ultra 27, 12 GB RAM, quad core 3.333 GHz Xeon, Nvidia
>> Q
Dr. David Kirkby wrote:
> javier wrote:
>
>> How about using this?
>>
>> #!/usr/bin/env python
>>
>> import sys
>> b = 1
>> x = sys.maxint
>>
>> while x:
>> x = x >> 1
>> b = b+1
>>
>> print(b)
>>
>>
>> Cheers
>> J
>
> It looks a bit better than a simple 32/64 result. 128 bit processors a
ma...@mendelu.cz wrote:
> Dear sage-devel
>
> If I run (with checked button "Typeset")
>
> maxima("taylor(z*sin(x*y), [x,y,z],[0,pi/2,1], 8)")
>
> in notebook in Sage 4.3, the output window is too small and I can see
> only small part of the expression. Is it a bug in CSS style or
> somwhere els
Dear sage-devel
If I run (with checked button "Typeset")
maxima("taylor(z*sin(x*y), [x,y,z],[0,pi/2,1], 8)")
in notebook in Sage 4.3, the output window is too small and I can see
only small part of the expression. Is it a bug in CSS style or
somwhere else?
Robert
--
To post to this group, sen
javier wrote:
> How about using this?
>
> #!/usr/bin/env python
>
> import sys
> b = 1
> x = sys.maxint
>
> while x:
> x = x >> 1
> b = b+1
>
> print(b)
>
>
> Cheers
> J
It looks a bit better than a simple 32/64 result. 128 bit processors are in
existence now, though not for genera
Jaap Spies wrote:
> David Kirkby wrote:
>> The following gives a rough idea of what works on Open Solaris on a
>> Sun Ultra 27. ( I say 'rough' as some packages I modified, and some
>> may not be working as they should).
>>
>> Hardware: Sun Ultra 27, 12 GB RAM, quad core 3.333 GHz Xeon, Nvidia
>> Q
guo tang wrote:
> On Mon, Jan 4, 2010 at 9:25 AM, Jaap Spies wrote:
>> guo tang wrote:
>>> Hi, Gentlemen,
>>>
>>> I am trying to build Sage 4.3 on RHEL4 but got the following error.
>>> Could anyone tell me how to solve it?
>>>
>>> Thanks,
>>> Guo
>>>
>>> uname -a
>>>
>>> Linux btl1lw24.btl.ms.phi
On 2010-Jan-03 22:52:46 +, "Dr. David Kirkby"
wrote:
>SAGE_FORTRAN_LIB=/path/to/fortran/libs/sparcv9/libgfortran.so
>(SPARC )
>
>SAGE_FORTRAN_LIB=/path/to/fortran/libs/amd64/libgfortran.so
>(Solaris x86/x64)
These paths seem likely. You also need to ensure that you install the
64-bit versio
Hi Georg,
Yes my sage folder is in /home/rado/ . Here is the output of 'which
cython'.
r...@rado-tablet:~$ which cython
/usr/bin/cython
sage subshell$ which cython
/home/rado/sage/local/bin/cython
/home/rado/sage
Any idea how to fix that issue ? I tried uninstalling my global cython
installatio
David Kirkby wrote:
> The following gives a rough idea of what works on Open Solaris on a
> Sun Ultra 27. ( I say 'rough' as some packages I modified, and some
> may not be working as they should).
>
> Hardware: Sun Ultra 27, 12 GB RAM, quad core 3.333 GHz Xeon, Nvidia
> Quadro FX 3800
> Software:
Mike Hansen wrote:
> Hello all,
>
> Sage 4.3.1.alpha0 is out. Source and binary areavailable at
>
> http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0.tar
> http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0-sage.math.washington.edu
On Mon, Jan 4, 2010 at 9:25 AM, Jaap Spies wrote:
> guo tang wrote:
>> Hi, Gentlemen,
>>
>> I am trying to build Sage 4.3 on RHEL4 but got the following error.
>> Could anyone tell me how to solve it?
>>
>> Thanks,
>> Guo
>>
>> uname -a
>>
>> Linux btl1lw24.btl.ms.philips.com 2.6.9-78.0.1.ELsmp #1
On Wed, Dec 30, 2009 at 01:10:05AM -0800, Robert Bradshaw wrote:
> > Does anyone know a trick to access the global variables for the "main"
> > scope?
> >
> > In the attached patch (for 4.2; untested on 4.3), I am implementing
> > the following in sage.misc.misc_c:
> >
> >def inject_variable(na
On Tue, Dec 29, 2009 at 12:28:46PM +, John Cremona wrote:
> 2009/12/29 Nathann Cohen :
> > Excellent ! Then
> >
> > __builtin__.sum([g,h],Graph())
> >
> > does the job.. Thank you :-)
Just 2 cents: in our code, we systematically use the following feature
from additive monoids:
sage: M
The following gives a rough idea of what works on Open Solaris on a
Sun Ultra 27. ( I say 'rough' as some packages I modified, and some
may not be working as they should).
Hardware: Sun Ultra 27, 12 GB RAM, quad core 3.333 GHz Xeon, Nvidia
Quadro FX 3800
Software: Open Solaris 06/2009. Based on sn
guo tang wrote:
> Hi, Gentlemen,
>
> I am trying to build Sage 4.3 on RHEL4 but got the following error.
> Could anyone tell me how to solve it?
>
> Thanks,
> Guo
>
> uname -a
>
> Linux btl1lw24.btl.ms.philips.com 2.6.9-78.0.1.ELsmp #1 SMP Tue Jul 22
> 18:01:05 EDT 2008 x86_64 x86_64 x86_64 GNU/Lin
Hi, Gentlemen,
I am trying to build Sage 4.3 on RHEL4 but got the following error.
Could anyone tell me how to solve it?
Thanks,
Guo
uname -a
Linux btl1lw24.btl.ms.philips.com 2.6.9-78.0.1.ELsmp #1 SMP Tue Jul 22
18:01:05 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
(cd /home/gtang/workdir/sage-4.
2010/1/4 Jason Grout :
> In light of a recent request on sage-support, can we make it very clear
> that the version of Sage on http://windows.sagemath.org/index.html is
> very experimental and not the standard, supported version of Sage (and
> redirect people to the Virtualbox image if they want th
On Sun, Jan 3, 2010 at 3:49 AM, Alex Ghitza wrote:
> On Sun, 3 Jan 2010 05:35:37 +, David Kirkby
> wrote:
>>
>> Was there a good reason for choosing the name 'sgn'? It sems a bit
>> strange to me.
>>
>
> That's the standard mathematical notation for this function, see
>
> http://en.wikipedia
2010/1/4 Jaap Spies :
> Dr. David Kirkby wrote:
>> Jaap Spies wrote:
>>
>>> As you stated before many spkgs are not in a good shape to handle this.
>
>>> Jaap
>>
>> I've raised tickets for some of these simple spkg-install fixes.
>>
>>
>> opencdk
>> http://trac.sagemath.org/sage_trac/ticket/7817
>>
-- Forwarded message --
From: Gonzalo Tornaria
Date: Thu, Dec 31, 2009 at 6:10 PM
Subject: Re: [sage-release] sage-4.3
To: sage-rele...@googlegroups.com
I haven't seen these reported:
$ \time ./sage -tp 16 devel/sage
...
The following tests failed:
sage -t devel/sage/sa
In light of a recent request on sage-support, can we make it very clear
that the version of Sage on http://windows.sagemath.org/index.html is
very experimental and not the standard, supported version of Sage (and
redirect people to the Virtualbox image if they want the "stable" Sage).
I think i
It does look like "descent_two_isogeny" is what it is failing to
compile, but I really can't help without more information. Is there a
way to get gcc to print out why it's failing?
It occurs to me that this depends on ratpoints, which has some issues
compiling with earlier versions of gcc. What ve
2010/1/4 Jaap Spies :
> Mike Hansen wrote:
>> Hello all,
>>
>> Sage 4.3.1.alpha0 is out. Source and binary areavailable at
>>
>> http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0.tar
>> http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.a
Dear colleague,
This is the first announcement for the conference to be held at CIRM,
Marseille, France, from February 22, 2010 to February 26, 2010.
++
| Sage Days 20 |
++
Sage
On 4 jan, 15:06, Jason Grout wrote:
> I'm curious where you see this eventually going?
>
> (1) MPComplexField replaces ComplexField
> (2) MPComplexField provides an alternative to ComplexField (this is
> what you're proposing right now, right?)
Yes, even if I would like (1) to happen in a far
Dr. David Kirkby wrote:
> Jaap Spies wrote:
>
>> As you stated before many spkgs are not in a good shape to handle this.
>> Jaap
>
> I've raised tickets for some of these simple spkg-install fixes.
>
>
> opencdk
> http://trac.sagemath.org/sage_trac/ticket/7817
>
> freetype:
> http://trac.sagemath.
YannLC wrote:
> Magma now uses MPC (
> http://magma.maths.usyd.edu.au/magma/htmlhelp/rel/node36.htm
> )
> Shouldn't we at least make it available in Sage ?
>
> (see ticket #4446)
>
I'm curious where you see this eventually going?
(1) MPComplexField replaces ComplexField
(2) MPComplexField
Magma now uses MPC (
http://magma.maths.usyd.edu.au/magma/htmlhelp/rel/node36.htm
)
Shouldn't we at least make it available in Sage ?
(see ticket #4446)
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr..
On Jan 4, 2:32 am, David Kirkby wrote:
> > Anyway, the following non-ctypes-code should do the same thing:
>
> > #!/usr/bin/env python
>
> > import sys
> > if sys.maxint > 2**32:
> > print "64"
> > else:
> > print "32"
>
> > -- William
>
> Thanks. I used to work on a Bruker NMR spectromete
Flint will not build in 64-bit mode on my Xeo based Open Solaris
machine, so I decided to look at the package.
In patches/makefile of the flint package there are a few things that
do not make a lot of sense to me. For the most part, the original
flint makefile makes more sence, though I gather thi
Mike Hansen wrote:
> Hello all,
>
> Sage 4.3.1.alpha0 is out. Source and binary areavailable at
>
> http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0.tar
> http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0-sage.math.washington.edu
It seems to be failing while compiling the cython code introduced by
#6583, so perhaps Robert Miller can help?
John
2010/1/4 Nathann Cohen :
> Hello everybody !!!
>
> I just noticed the compilation of alpha0 on my computer failed... And
> I am afraid I have no idea how to inquire where it comes f
2010/1/4 Jaap Spies :
> Dr. David Kirkby wrote:
> [...]
>>
>> Failed to find the necessary bits to build these modules:
>> _bsddb _hashlib _ssl
>> bsddb185 dl gdbm
>> imageop linuxaudiodev ossaudiodev
>> To find the necessary bits, loo
Hello everybody !!!
I just noticed the compilation of alpha0 on my computer failed... And
I am afraid I have no idea how to inquire where it comes from... I can
give you the last few lines of the install log, and you but have to
ask me which other information you may need ( and tell me how to
obta
Dr. David Kirkby wrote:
[...]
>
> Failed to find the necessary bits to build these modules:
> _bsddb _hashlib _ssl
> bsddb185 dl gdbm
> imageoplinuxaudiodev ossaudiodev
> To find the necessary bits, look in setup.py in detect_modules(
Alex Ghitza wrote:
> On Sun, 3 Jan 2010 05:35:37 +, David Kirkby
> wrote:
>> Was there a good reason for choosing the name 'sgn'? It sems a bit
>> strange to me.
>>
>
> That's the standard mathematical notation for this function, see
>
> http://en.wikipedia.org/wiki/Sign_function
Then the
I'm working on the unicode stuff right now. Hopefully this will be done
before the end of this week.
On Mon, Jan 4, 2010 at 8:12 AM, Dan Drake wrote:
> On Sun, 03 Jan 2010 at 08:17AM -0800, ma...@mendelu.cz wrote:
> > I think that it would be nice to allow localization of notebook. I
> > have se
Hello all,
Sage 4.3.1.alpha0 is out. Source and binary areavailable at
http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0.tar
http://sage.math.washington.edu/home/mhansen/release/4.3.1/alpha0/sage-4.3.1.alpha0-sage.math.washington.edu-x86_64-Linux.tar.gz
The upg
63 matches
Mail list logo