> One option I believe will work is to put the scripts in
>
> $SAGE_ROOT/spkg/base/
>
> then update $SAGE_ROOT/spkg/install so it copies the scripts to
> $SAGE_LOCAL/bin. The only change needed to the $SAGE_ROOT/spkg/install
> script is from
>
> cp base/sage-* "$SAGE_LOCAL/bin/"
>
> to
>
> c
I've asked this before, but have received no response, so I thought I'd try
again.
Numerous bits of Sage use options to the compiler. Those options often need to
change depending on the compiler in use. For example, -fPIC is a GNU-specific
option which is commonly used in Sage. -m64 works for G
On 2009-Dec-13 16:27:41 +, "Dr. David Kirkby"
wrote:
>If you have a system with the GNU version of date, then
>
>date -u +%s
>
>will give the seconds since the Epoch. Unfortunately, it only works with GNU
>date, and so will not work on Solaris, HP-UX or no doubt many other Unix
>systems.
F
Hi Martin!
I am not an expert for imap.
But look at iparith.cc.
if ((w=r->idroot->get(v->Name(),myynest))!=NULL){
...}
else
{
Werror("identifier %s not found in %s",v->Fullname(),u->Fullname());
}
First we have to understand, what imap does...
pure Singular.
> ring r=0,(x,y,z),dp;
> poly
I've had some error messages whilst trying to create a binary distribution of
Sage on Solaris. cp is complaining about broken link.
So I decided to build Sage on linux and see if the link is broken there too,
which it is.
kir...@sage:~/sage-4.3.rc0/local/lib/python2.6$ ls -l python2.6
lrwxrwxr
Hi Chris,
On Sun, Dec 13, 2009 at 9:30 PM, chris wuthrich
wrote:
>
> Thanks a lot for this tutorial. I think it would be great to have it
> included in the documentation.
See ticket #7679 [1] for a patch to enhance the Constructions document
with this tutorial.
[1] http://trac.sagemath.org/sag
> Personally, I'm against disagree with tests being run this way in the
> Sage doctest test suite.
> I think such randomized testing should be done totally separately,
> e.g., as is done in the modular/modsym/tests.py file. I think there
> should be a huge range of randomized testing that gets ru
2009/12/13 Robert Miller :
> Originally, refinement_matrices etc. were set up to run tests for a
> certain amount of time, but several machines on boxen which we run
> tests on have really messed up clocks (10-30 seconds of real time
> correspond to about 1 second of their clock time), so we couldn
Originally, refinement_matrices etc. were set up to run tests for a
certain amount of time, but several machines on boxen which we run
tests on have really messed up clocks (10-30 seconds of real time
correspond to about 1 second of their clock time), so we couldn't rely
on that.
So the decision w
> I will do groups/perm_gps/partn_ref/ next. It's taking a bit longer
> because I think I ran into some issues with refinement_matrices.pyx.
What are the issues? I can take care of partn_ref if you want...
--
Robert L. Miller
http://www.rlmiller.org/
--
To post to this group, send an email t
Dear Robert,
I was trying to see if I can shorten the randomized doctests in
refinement_*.pyx, and I noticed two things that seem odd (to me, since
I have no knowledge of the algorithms or implementation details for
these files).
1. The time that the random tests take (with the same values of th
Gael Varoquaux wrote:
> ==
> Announcing EuroScipy 2010
> ==
>
> ---
> The 3rd European meeting on Python in Science
> ---
>
> **Paris, Ecole Normale Supéri
On Sun, Dec 13, 2009 at 11:01:14AM -0800, William Stein wrote:
>
> +1 to shortening/marking #long those doctests Alex mentioned.
>
OK, the first patch, dealing with the Bernoulli numbers tests in
arith.py, is up at
http://trac.sagemath.org/sage_trac/ticket/7678
I will do groups/perm_gps/partn_
Wouldn't one of you love to review a 3-digit ticket? (There are 6
with smaller numbers, including 3 with 3 digits, but this one is three
years old.)
John
--
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.
Here's a list of the dates on the 'src' directory of each .spkg file which has
a
'src' directory - which is most of them. The oldest is shown first. Below
this, is the script for finding these, which is far from elegant, but works.
I'm assuming the date on the 'src' directory is the date of t
Thanks a lot for this tutorial. I think it would be great to have it
included in the documentation.
I did not know anything about functional programming before using
sage. To a new mathematical user without python knowledge things like
lambda = 4
SyntaxError: invalid syntax
lambda?
No object 'l
2009/12/13 William Stein :
>> 7514 schemes/elliptic_curves/ell_rational_field.py
>>
>> Some of these could (should?) probably be split up a bit.
>
> +1 to shortening/marking #long those doctests Alex mentioned.
>
> Also, trac 6616 splits up ell_rational_field.py by removing all the
> Heegner poi
On Thu, Dec 10, 2009 at 7:18 PM, Mike Hansen wrote:
> Hello all,
>
> Sage 4.3.rc0 is out. Source and binary are available at
>
I did a build test on OS X 10.5 PPC and there are some problems I
think not mentioned elsewhere. The first is a badly written doctest
by somebody who didn't think about
On Sun, Dec 13, 2009 at 3:00 AM, John Cremona wrote:
> This all sounds very sensible. Another related point is that some
> individual files are very very long. For example, one of the 10 files
> in your list is sage/schemes/elliptic_curves/ell_rational_field.py
> which is 7514 lines long, more t
Dr. David Kirkby wrote:
> If you have a system with the GNU version of date, then
>
> date -u +%s
>
> will give the seconds since the Epoch. Unfortunately, it only works with GNU
> date, and so will not work on Solaris, HP-UX or no doubt many other Unix
> systems.
>
> The following script shou
If you have a system with the GNU version of date, then
date -u +%s
will give the seconds since the Epoch. Unfortunately, it only works with GNU
date, and so will not work on Solaris, HP-UX or no doubt many other Unix
systems.
The following script should compute this is a portable manner. Here
On Dec 13, 1:02 am, Minh Nguyen wrote:
> I have written a draft of a tutorial on functional programming for
> mathematicians.
Very nice, i added a comment and I just repeat it here. I think you
should also point to the "operator" python package, since defining add
in a function is an overhead and
If you convert to numpy matrices, then Sage is pretty competitive with
matlab. We still have some room for improvement in making it easy
though - despite Jason Grout's improvements, a matrix over RDF is
missing some methods I'd like, such as the singular value
decomposition. As an example, to ext
Sounds like a very good idea. To be on the safe side, we could just
move existing doctests that take a while to the "# long time" option,
and then they would still get tested. Usually it seems that with some
tweaks like you propose to arith.py many doctests can be sped up.
-Marshall
On Dec 12,
This all sounds very sensible. Another related point is that some
individual files are very very long. For example, one of the 10 files
in your list is sage/schemes/elliptic_curves/ell_rational_field.py
which is 7514 lines long, more than double the next longest in that
directory. (I have writte
On Sat, Dec 12, 2009 at 11:29 PM, Juan Jose Garcia-Ripoll <
juanjose.garciarip...@googlemail.com> wrote:
> Streams may be opened with either ANSI C streams (fopen) or with C file
> descriptors (open). The later is needed for sockets and certain devices,
> while the formers provide buffering and ma
On Sat, Dec 12, 2009 at 11:09 PM, Minh Nguyen wrote:
> Hi David,
>
> On Sun, Dec 13, 2009 at 11:20 AM, David Joyner wrote:
>
>
>
>> I think this would fit nicely in the constructions document.
>> Adding an example of how to use map for Sage matrices might
>> be worth thinking about.
>
> I have p
27 matches
Mail list logo
