Hi folks,
Aaron Seigo has an interesting blog post on communication:
http://aseigo.blogspot.com/2009/09/continuous-communication.html
It talks in some detail about communication within a FOSS project,
finding opportunities to reach beyond the existing audiences of the
project, and maintaining c
Hi folks,
I need to devote some serious time to my thesis project starting 01st
October 2009. Before doing that, I would like to wrap up an rc0
release for Sage 4.1.2. Unfortunately, due to the 2 month deadline of
my thesis submission date, I will need to take a break from release
management star
On 2009-Sep-27 06:32:41 -0700, Marmaduke wrote:
>I learned most useful things from the Info pages on coreutils. Maybe
>these can be rendered to html because they come from Texinfo?
I'd strongly recommend against using the coreutils or bash info
files as a basis for learning Unix. Virtually all G
On Mon, Sep 28, 2009 at 8:44 PM, Dr. David Kirkby
wrote:
>
> The title pretty much says it all. I edited the Makefile to remove the line
>
> CC=gcc
>
> then exported CC to /usr/sfw/bin/gcc
>
> which is version 3.4.3 of gcc.
It builds with different options and optimizations (and even code?) on
L
The title pretty much says it all. I edited the Makefile to remove the line
CC=gcc
then exported CC to /usr/sfw/bin/gcc
which is version 3.4.3 of gcc.
I did this outside of Sage - just decompressed the .spkg and run
spkg-install.
As you can see below, ratpoints builds fine.
drkir...@swan:
William Stein wrote:
> Minh,
>
> We've reopened #6759 -- update sqlite -- since it doesn't work on
> Cygwin, whereas the version in Sage works fine on Cygwin:
>
> http://trac.sagemath.org/sage_trac/ticket/6759
>
> William
>
For reasons I do not understand, I am unable to edit the ticket. I w
Minh,
We've reopened #6759 -- update sqlite -- since it doesn't work on
Cygwin, whereas the version in Sage works fine on Cygwin:
http://trac.sagemath.org/sage_trac/ticket/6759
William
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
--~--~--
I found the rubiks package would not build on Solaris with the Sun
compiler. After looking at it, this seems to be one of the worst
packages I've ever seen. It's a miracle it worked on any platform.
* g++ was hard coded
* SAGE64 was not used at all.
* CFLAGS was set when really it should
On Mon, 28 Sep 2009 at 07:10AM -0700, Mariah wrote:
> If this is acceptable, would a kind developer check this in.
I converted your patch to our Mercurial format and posted it at ticket
#4644, and left a comment on ticket #5507.
Dan
--
--- Dan Drake
- http://mathsci.kaist.ac.kr/~drake
---
On Mon, Sep 28, 2009 at 12:27 PM, ahmet alper parker wrote:
>
> On Sun, Sep 27, 2009 at 10:37 AM, William Stein wrote:
>>
>> On Sun, Sep 27, 2009 at 12:13 AM, Minh Nguyen wrote:
>>>
>>> Hi folks,
>>>
>>> Ticket #6580 [1] is meant to have ratpoints build with GCC 3.4.x. The
>>> Sage build farm u
On Mon, Sep 28, 2009 at 1:07 PM, Jason Grout wrote:
>
> Jonathan wrote:
>> This appears to be a SAGE specific problem. I can even reproduce it
>> with Firefox on MacOS (works fine in Safari on MacOS). There must be
>> something about the javascript used to launch Jmol. I will need to
>> delve i
Try Andy Booker at Bristol -- I don't remember which language he and
his students are using.
You didn't give Norm Hurt's email, so please forward this to him.
I am CC-ing sage-nt as perhaps a better place for the thread.
John
2009/9/28 David Joyner :
> I am forwarding this to sage-devel at the
On Sun, Sep 27, 2009 at 10:37 AM, William Stein wrote:
>
> On Sun, Sep 27, 2009 at 12:13 AM, Minh Nguyen wrote:
>>
>> Hi folks,
>>
>> Ticket #6580 [1] is meant to have ratpoints build with GCC 3.4.x. The
>> Sage build farm uses GCC >= 4.0.1 and ticket #7021 [2] has the updated
>> package prereq-
Hi,
I looked over the code. The code implements what is the world's
fastest general purpose prime_pi for a practical range of numbers --
it's much faster than Mathematica, or anything else available in
general purpose software. However, it is really mainly a first very
rough draft, in that it st
On Sep 28, 2:53 pm, Pat LeSmithe wrote:
> On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
> > * Re-organize the Sage wiki front page? For example:
>
> There's a very early version at
>
> http://wiki.sagemath.org/NewFrontPage
What a massive improvement in organization this would be! T
> On Mon, Sep 28, 2009 at 7:57 AM, John Cremona wrote:
>
> > Two test failures on 32-bit ubuntu:
>
> > sage -t "devel/sage/sage/crypto/boolean_function.pyx"
>
> > sage -t "devel/sage/sage/rings/polynomial/pbori.pyx"
The former already has a positive review at trac #7020, and latt
On Sun, Sep 27, 2009 at 11:16 AM, Pat LeSmithe wrote:
> * Re-organize the Sage wiki front page? For example:
There's a very early version at
http://wiki.sagemath.org/NewFrontPage
Feel free to make suggestions and changes to this page or to any of
http://wiki.sagemath.org/SageSupportCenter
h
I found Sage 4.1.2.a4 to compile fine on an intel macbok running 10.6.
he folowing doctests failed:
The following tests failed:
sage -t "devel/sage/sage/calculus/calculus.py"
sage -t "devel/sage/sage/calculus/tests.py"
sage -t "devel/sage/sage/calculus/wester.py"
Hello,
If I am right, the symbolic manipulations of Sage come from the
(py)ginac librairies.
In ginac documentation I find very intersting functions for my use of
expressions :
is_a
is_a
is_a
There are about 30 tests for possible types.
The types I can test by Expression.any_tests_I_find_iw
Hi William,
Sorry i didn't notice the rating mechanism, I've been having trouble
logging into sagenb due to some settings in my browser, I think. So i
was writing from memory.
Thanks!
Hazem
On Sep 28, 12:31 pm, William Stein wrote:
> On Mon, Sep 28, 2009 at 9:14 AM, Hazem wrote:
>
> > Hi,
>
On Sep 28, 2009, at 9:31 AM, John Cremona wrote:
>
> Try instead the press release from the U of Warwick:
> http://www2.warwick.ac.uk/newsandevents/pressreleases/
> warwick_mathematician_helps/
>
> which I had been meaning to post but otherwise engaged. This was the
> first big job run on "selm
Jonathan wrote:
> This appears to be a SAGE specific problem. I can even reproduce it
> with Firefox on MacOS (works fine in Safari on MacOS). There must be
> something about the javascript used to launch Jmol. I will need to
> delve into how SAGE uses Jmol... As I haven't looked at this before
On Mon, Sep 28, 2009 at 9:35 AM, John Hunter wrote:
> On Mon, Sep 28, 2009 at 11:14 AM, John Hunter wrote:
>
>> But even simple tests are failing with::
>>
>> jdh2...@bsd:~> LD_LIBRARY_PATH=~/devtest/lib/
>> PYTHONPATH=~/devtest/lib/python2.6/site-packages/ /usr/bin/python -c
>> 'import matplotl
On Mon, Sep 28, 2009 at 11:14 AM, John Hunter wrote:
> But even simple tests are failing with::
>
> jdh2...@bsd:~> LD_LIBRARY_PATH=~/devtest/lib/
> PYTHONPATH=~/devtest/lib/python2.6/site-packages/ /usr/bin/python -c
> 'import matplotlib; matplotlib.use("Agg"); from matplotlib.pyplot
> import *;
On Mon, Sep 28, 2009 at 9:29 AM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>> On Sun, Sep 27, 2009 at 2:12 PM, Dr. David Kirkby
>> wrote:
>>> William Stein wrote:
>>>
> Just to add that even the very latest release of Solaris (Solaris 10
> update 7) on SPARC only ships with gcc 3.
On Mon, Sep 28, 2009 at 9:14 AM, Hazem wrote:
>
> Hi,
>
> Something like FileExhange already exists for Sage - The published
> Sage worksheets on the Sagenb site. I think it should be featured more
> prominently on the main Sage site and elsewhere. The worksheets can be
> inspected without login,
Try instead the press release from the U of Warwick:
http://www2.warwick.ac.uk/newsandevents/pressreleases/warwick_mathematician_helps/
which I had been meaning to post but otherwise engaged. This was the
first big job run on "selmer", the new machine Bill Hart and I bought
(using his grant and
William Stein wrote:
> On Sun, Sep 27, 2009 at 2:12 PM, Dr. David Kirkby
> wrote:
>> William Stein wrote:
>>
Just to add that even the very latest release of Solaris (Solaris 10
update 7) on SPARC only ships with gcc 3.4.3. Users using SPARC
hardware are unlikely to have root acc
On Mon, Sep 28, 2009 at 9:14 AM, John Hunter wrote:
> On Mon, Sep 28, 2009 at 10:48 AM, William Stein wrote:
>> If you could just try running your matplotlib build on
>> bsd.math.washington.edu and reporting about whether or not it works,
>> that would be very helpful, since it will indicate whe
Hi,
Something like FileExhange already exists for Sage - The published
Sage worksheets on the Sagenb site. I think it should be featured more
prominently on the main Sage site and elsewhere. The worksheets can be
inspected without login, although to contribute you need to log in.
However, I thin
Dr. David Kirkby wrote:
> I've created an update of prereq from 0.3 to 0.4 which does the
> preliminary checks of the Sage build.
>
> http://sagetrac.org/sage_trac/ticket/7021
I've updated that again, taking into account some comments.
* Check's for the program 'ar' as that is needed.
* Infor
On Mon, Sep 28, 2009 at 8:55 AM, William Stein wrote:
> On Mon, Sep 28, 2009 at 8:47 AM, John Hunter wrote:
>> -- Forwarded message --
>> From: Tony S Yu
>> Date: Mon, Sep 28, 2009 at 8:41 AM
>> Subject: Re: [matplotlib-devel] Fwd: OS X 10.6 port
>> To: John Hunter
>> Cc: matpl
On Mon, Sep 28, 2009 at 8:47 AM, John Hunter wrote:
> -- Forwarded message --
> From: Tony S Yu
> Date: Mon, Sep 28, 2009 at 8:41 AM
> Subject: Re: [matplotlib-devel] Fwd: OS X 10.6 port
> To: John Hunter
> Cc: matplotlib development list
>
>
>
> On Sep 28, 2009, at 2:14 AM, Jo
On Mon, Sep 28, 2009 at 4:54 AM, John Hunter wrote:
> On Mon, Sep 28, 2009 at 4:47 AM, Dr. David Kirkby
> wrote:
>> William Stein wrote:
>>>
>>> Hi,
>>>
>>> I spent several hours yesterday trying to get matplotlib for Sage to
>>> work on OS X 10.6. On my laptop everything works perfectly, but o
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit Mandriva Linux 2009.0
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: mandriva32 virtualized guest on boxen.math
The following doctests fail:
{{{
sage -t -long "dev
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Mandriva Linux 2009.0
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: mandriva64 virtualized guest on boxen.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Debian GNU/Linux 5.0
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: debian5-64 virtualized guest on boxen.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~-
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit Debian GNU/Linux 5.0
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: debian5-32 virtualized guest on boxen.math
The following doctests fail:
{{{
sage -t -long "deve
On Sep 28, 6:09 am, Minh Nguyen wrote:
> Hi folks,
>
> Sage 4.1.2.alpha4 compiles OK on the following platform:
>
> * Operating system: Mac OS X 10.6
> * CPU: Dual-Core Intel Xeon, 2.66 GHz
> * RAM: 8 GB
> * Computer name: bsd.math
>
> The following doctests failed, most of which are due to a "my
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Ubuntu 9.04
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: ubuntu64 virtualized guest on boxen.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~--~-
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit Ubuntu 9.04
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: ubuntu32 virtualized guest on boxen.math
The following doctests fail:
{{{
sage -t -long "devel/sage/sage
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Ubuntu 8.04.3 LTS
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 124 GB
* Computer name: sage.math
All doctests pass.
--~--~-~--~~~---~--~~
To post to th
Michael Droettboom wrote:
> This is a very long-standing bug in distutils:
>
> http://bugs.python.org/issue1222585
>
> While distutils distinguishes between C and C++ for *linking*, it does
> not do so for *compiling*. This doesn't matter for gcc and msvc (which
> are arguably the two most
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit Ubuntu 9.04
* CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz
* RAM: 1 GB
The following doctests fail:
{{{
sage -t -long "devel/sage/sage/rings/polynomial/pbori.pyx"
***
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Fedora 9
* CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz
* RAM: 8 GB
* Computer name: eno on SkyNet
The following doctests fail:
{{{
sage -t -long "devel/sage/sage/server/introspect.py"
A myste
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Red Hat Enterprise Linux Server 5.3
* CPU: AMD Phenom(tm) II X4 940 Processor with NVIDIA GeForce GPUs
* RAM: 16 GB
* Computer name: lena on SkyNet
All doctests pass.
--
Regards
Minh Van Nguyen
--~-
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Fedora 10
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: fedora64 virtualized guest on boxen.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~--~-~-
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit Fedora 10
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: fedora32 virtualized guest on boxen.math
The following doctests fail:
{{{
sage -t -long "devel/sage/sage/c
Minh suggests that developers would prefer to have
the current directory listed in a sage sub-shell prompt.
The patch below causes the current directory to be
listed on one line and then "sage subshell$ " on the
next. Hopefully this will help people like Paulo
remember when they are in a sage su
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit Red Hat Enterprise Linux Server 5.4
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 124 GB
* Computer name: rosemary.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~--~-~
On Mon, Sep 28, 2009 at 11:51 PM, Minh Nguyen wrote:
> Hi folks,
>
> Sage 4.1.2.alpha4 compiles OK on the following platform:
>
> * Operating system: 64-bit openSUSE 11.1
> * CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz
> * RAM: 8 GB
> * Computer name: menas on SkyNet
I should mention th
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit CentOS 5.2
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: centos64 virtualized guest on boxen.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~--~-~
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit CentOS 5.2
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: centos32 virtualized guest on boxen.math
The following doctests fail:
{{{
sage -t -long "devel/sage/sage/
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit openSUSE 11.1
* CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz
* RAM: 8 GB
* Computer name: menas on SkyNet
All doctests pass.
--
Regards
Minh Van Nguyen
--~--~-~--~~~-
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 64-bit openSUSE 11.1
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: opensuse64 virtualized guest on boxen.math
All doctests pass.
--
Regards
Minh Van Nguyen
--~--~-
On Mon, Sep 28, 2009 at 11:19 PM, Minh Nguyen wrote:
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit openSUSE 11.1
* CPU: Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
* RAM: 1 GB
* Computer name: opensuse32 virtualized guest on boxen.math
> The followin
On Fri, Sep 25, 2009 at 08:52:48PM -0700, Pat LeSmithe wrote:
> >> I'm not an expert, but in case it helps: It seems that pyparsing is
> >> already included with matplotlib. However, the import statement needs
> >> to be qualified:
> >>
> >> sage: import matplotlib.pyparsing
> >
> > Ah ah, than
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit Fedora 9
* CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz
* RAM: 1 GB
* Computer name: cicero on SkyNet
The following doctests fail:
{{{
sage -t -long "devel/sage/sage/misc/randstate.pyx"
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: 32-bit openSUSE 11.0
* CPU: Intel(R) Core(TM)2 Duo CPU E4600 @ 2.40GHz
* RAM: 5 GB
* Computer name: caruso
The following doctests fail:
{{{
sage -t -long "devel/sage/sage/rings/polynomial/pbori.pyx"
[?
Hi folks,
Sage 4.1.2.alpha4 compiles OK on the following platform:
* Operating system: Mac OS X 10.6
* CPU: Dual-Core Intel Xeon, 2.66 GHz
* RAM: 8 GB
* Computer name: bsd.math
The following doctests failed, most of which are due to a "mysterious
error". The full log shows many occurrences of t
When upgrading from 4.1.2.alpha2, I had to commit a change to
something about primes in extcode. I should have written it down -
sorry. Did anyone else see this?
- kcrisman
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
Minh Nguyen wrote:
> Hi Japp,
>
> On Mon, Sep 28, 2009 at 5:29 AM, Jaap Spies wrote:
>
>
>
>> On Fedora 11, 32 bit build failed on sage:
>> An error occurred while installing pari-2.3.3.p1
>>
>> I had a fix for alpha1 but this did not get into alpha4
>> apparently.
>
> I don't remember seei
William Stein wrote:
> Hi,
>
> I spent several hours yesterday trying to get matplotlib for Sage to
> work on OS X 10.6. On my laptop everything works perfectly, but on
> another test machine (bsd.math) the workaround from my laptop doesn't
> work. So at this point Sage still does not support O
I run upgrade from a sage-4.1.1 built at home on an ubuntu jaunty with a
dual-core pentium by
./sage -upgrade
http://sage.math.washington.edu/home/mvngu/release/upgrade/sage-4.1.2.alpha4
Then I get an error with an unknown function PC when I ran the updated sage.
The ticket #6990 gives a new
On Sep 28, 10:38 am, Maurizio wrote:
> Can't we take advantage of inheritance for this issue? I don't know
> how far that can go, though, I'm not a programmer...
>
> Thanks
>
> Maurizio
I think this will cause headaches to non-programmers, if your idea of
dependence does not agree with the compu
Hi!
On Sep 28, 12:22 am, Jaap Spies wrote:
> Found this on the web: A Trillion Triangles
>
> http://www.aimath.org/news/congruentnumbers/
The article mentions that they used free software, but it is not
named. In fact, according to that article, Sage is a computer at the
university of Washingto
Can't we take advantage of inheritance for this issue? I don't know
how far that can go, though, I'm not a programmer...
Thanks
Maurizio
On Sep 28, 9:40 am, William Stein wrote:
> On Mon, Sep 28, 2009 at 12:11 AM, Maurizio wrote:
>
> > First of all, thank you for the example!
>
> >> I'm prett
On Mon, Sep 28, 2009 at 12:11 AM, Maurizio wrote:
>
> First of all, thank you for the example!
>
>>
>> I'm pretty sure it is impossible to decide whether a cells output depends on
>> the
>> value of a given variable. You could get it write some of the time by seeing
>> if the variable appears,
First of all, thank you for the example!
>
> I'm pretty sure it is impossible to decide whether a cells output depends on
> the
> value of a given variable. You could get it write some of the time by seeing
> if the variable appears, but given the dynamic nature of Python it is
> impossible to
69 matches
Mail list logo
