On Apr 23, 9:34 pm, Jason Grout wrote:
> Carl Witty wrote:
> > On Thu, Apr 23, 2009 at 9:19 PM, Jason Grout
> > wrote:
> >> Anyone know where the CSS file is? The color is set in a default.css
> >> file, but the only default.css files I see are in _static directories,
> >> which sounds like t
On Apr 23, 10:34 pm, Tim Abbott wrote:
> On Thu, 23 Apr 2009, mabshoff wrote:
Hi Tim,
> > Another thing: In 3.4.1 we downgraded GAP to 4.4.10 from 4.4.12 that
> > was upgraded in Sage 3.3 due to a significant number of bugs and
> > issues in GAP 4.4.12. How would you dea
On Apr 23, 10:57 pm, Tim Abbott wrote:
> On Thu, 23 Apr 2009, mabshoff wrote:
> > I doubt this will ever happen. Soon for example we plan to switch to
> > the svn version of pari which absolutely changes lots of things in
> > Sage in non-backward compatible ways, so you
On Apr 24, 12:19 am, "Dr. David Kirkby"
wrote:
> mabshoff wrote:
Hi David,
> > OK. Not that for gcc 4.2.2 the gfortran creates completely broken code
> > on Sparc, so the only toolchain I will be using is the one specified
> > above since it is well tested
On Apr 24, 1:16 am, John Cremona wrote:
Hi,
> This problem has been around for a while. It works ok if you give an
> absolute pathname.
>
> Having said that, I just realised that the testing I have been doing
> on a clone of 3.4.1 was working fine with a relative pathname.
>
> Perhaps it is
both into alpha0.
The source, upgrade bits and a sage.math-only binary should be
available in
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.2/
>From here on the plan is to merge other reviewed patches (in case you
are bored, there are about 80 patches to review in t
Hello folks,
by accident I build my 3.4.2.alpha0 build as an SSE2 only build. So I
had a change to play with it a little and check for performance
regressions. Here are some basic benchmarks:
SSE2 vs. SSE3:
* measurable difference for ZZ determinant (~10% slower with SSE2 for
300x300, 400x400,
On Apr 22, 11:40 pm, Minh Nguyen wrote:
> Hi Michael,
Hi Minh,
> My policy thus far is to list the author(s) of the patch(es). The case
> you mentioned above was a result of me misreading ticket #5146. This
> is because for the patch variety_patch.3.patch, I saw the description
> "Updated wit
On Apr 24, 4:10 am, Lloyd Kilford wrote:
Hi Lloyd,
> I have downloaded the images of versions 3.4 and 3.4.1 to run under
> VMware, but I get the following error message when I try to run sage:
>
> WARNING: This Sage install was built on a machine that supports
> instructions that are not ava
On Apr 24, 5:56 am, Burcin Erocal wrote:
> On Wed, 22 Apr 2009 14:42:21 -0700 (PDT)
Hi Burcin,
> On tickets which have a traceback, this screws up my display. The page
> width grows to accommodate the longest line in the traceback, forcing me
> to scroll right/left to read long lines.
>
> S
On Apr 24, 5:43 am, prof wrote:
> Hello,
Hi,
> I have installed Sage as root on iMac/Leopard 10.5.6 from sources
> using the normal procedure (tar, make, make test...). Everything looks
> ok. Sage was installed on /Applications/sage-3.4/. Using Sage as a
> normal user at Terminal:
> cd /Appli
On Apr 24, 11:27 am, Tim Abbott wrote:
Hi Tim,
> On Thu, 23 Apr 2009, Jason Grout wrote:
> > Jqueryui can actually be updated to the latest release, which is later
> > than the svn version shipping with Sage, so that shouldn't be a problem.
> > Matplotlib should be releasing a new version
On Apr 24, 2:12 pm, Ben Goodrich wrote:
> On Apr 24, 2:27 pm, Tim Abbott wrote:
Hi Ben,
> On the issue of using pre-release versions of Sage dependencies,
> perhaps as a last resort we could ask Debian package maintainers to
> upload a SVN version to the experimental repository and a reaso
On Apr 24, 11:26 am, Tim Abbott wrote:
> On Thu, 23 Apr 2009, mabshoff wrote:
Hi Tim,
> > Well, you pushed patches upstream that contain GNUisms and I will end
> > up patching it out of the sources again, so I am not too happy about
> > that since upstream way too ofte
On Apr 24, 2:50 pm, Ben Goodrich wrote:
Hi Ben,
> Right, anyone (mostly servers) using Debian stable or oldstable is not
> going to be able to keep up with Sage easily.
Agreed, but I think you misjudge the number of people running Debian
stable on non-server scenarios. It is also quite com
On Apr 24, 3:07 pm, David Harvey wrote:
> On Apr 24, 2:26 pm, Tim Abbott wrote:
Hi David,
> > As I understand it, David Harvey isn't physically at NYU yet and nobody
> > had mentioned the patch to Victor prior to my sending it to Victor.
>
> Actually, I've been physically at NYU since last J
On Apr 24, 3:09 pm, mabshoff wrote:
> On Apr 24, 2:50 pm, Ben Goodrich wrote:
> So the following packages need to be sorted out:
>
> * numpy to 1.3
> * scipy to 0.7 (maybe 0.7.1 if it is out by then)
> * NTL to 5.5
> * jquery
> * matplotlib (I know they have be
On Apr 24, 3:30 pm, Tim Abbott wrote:
> On Fri, 24 Apr 2009, mabshoff wrote:
Hi Tim,
> > Is that correct or are the GNUisms Victor's fault?
>
> I would assume that is correct. I didn't actually write any of the code
> for NTL 5.5; Victor did all the work ther
On Apr 24, 5:27 pm, "Nicolas M. Thiery"
wrote:
> On Fri, Apr 24, 2009 at 01:23:25AM -0700, mabshoff wrote:
Hi Nicolas,
> > I remember a discussion about the problem, but did not see any fixes
> > in 3.4.1. If someone knows a ticket and/or even better a patch please
On Apr 24, 6:27 pm, Gonzalo Tornaria wrote:
Hi Gonzalo,
> On Fri, Apr 24, 2009 at 10:06 PM, mabshoff wrote:
> > Gonzalo: Can you please post a proper patch for bugfixes you suggest -
> > I am happt to convert your diff into a proper patch attributed to you,
> > but if you
On Apr 24, 6:24 pm, Rado wrote:
> Hello,
Hi Rado,
> I was trying to load some python files and found some weird behaviour
> of the load/attach commands. I have three test files
>
> (a normal file) /home/rado/.sage/test.py
> (a file with space in the name) /home/rado/.sage/test space.py
> (a f
On Apr 24, 11:01 pm, Minh Nguyen wrote:
> Hi Michael,
Hi Minh,
> for the release tour of Sage 3.4.1, David Loeffler has put down Georg
> S. Weber, Chris Kurth and himself as contributors of code for that
> ticket. The patch 5180-arithgroups.patch on that ticket certainly has
> Chris Kurth as
pears the
> directory /home/mabshoff/sparc-solaris-toolchain/ is hard-coded
> somewhere, so naturally fails if the build-directory is elsewhere:
Find lib/libstdc++.la in the toolchain directory and fix the path. You
might want to look for other libtool generated files (i.e. various .la
file
On Apr 24, 11:51 pm, "Nicolas M. Thiery"
wrote:
> > > For information: the patch suggested on #5852 seems to work fine on my
> > > machine (macbook pro ubuntu intrepid)
>
> > Well, give the complexity of the patch why did you not do a formal
> > review then? :)
>
> I got scared by your comments
Hello folks,
nearly all binaries for 3.4.1 are available in http://www.sagemath.org/bin/
(as the title says). All x86 and x86-64 Linux binary as well as the
VMWare image are now SSE2 only, i.e. there are some performance
regressions as mentioned yesterday in a thread here, for example RDF
matrix
On Apr 25, 2:15 am, ahmet alper parker wrote:
> Hi All,
>
> Is there anyone who has knowledge about it and its possible future
> benefits to scientific computing (especially for sage + maxima etc.)
> of the GPU computing with the new Nvidia Tesla platform?
>
> http://www.nvidia.com/object/tesla
On Apr 25, 12:13 am, "Nicolas M. Thiery"
wrote:
> On Wed, Apr 22, 2009 at 06:24:38PM -0700, mabshoff wrote:
Hi Nicolas,
> I really would want to get the category code in Sage soon (4.0???):
At this stage I do believe you might have a hard time getting this
into 4.0 give
On Apr 25, 10:04 am, Jonathan Hanke wrote:
> Hi,
>
> I'm having trouble with building gmp-mpir in sage 3.4.1 on my Mac Pro. I
> have previously successfully built 3.1.2 without any difficulty. Any
> comments are appreciated. Thanks,
>
> -Jon
> =)
Hi Jon,
The issue is known and has been fi
On Apr 25, 2:44 pm, Tim Abbott wrote:
> Hello,
Hi Tim,
> I was wondering why boehm_gc is a standard Sage package. It seems that it
> isn't actually a dependency of anything in spkg/standard/deps; is that
> because it is only used by the sage library and a there's a missing
> dependency, or i
On Apr 25, 5:53 am, David Joyner wrote:
Hi David,
> Wow! I have stunning news (for me anyway):
>
> This compiles perfectly *and passes all tests* on ubuntu 64bit 8.10
> with a phenom chip.
Well, give the trouble you have seen in the past with your specific
setup this clearly indicates clisp si
On Apr 25, 7:30 pm, kcrisman wrote:
Hi,
> Builds from scratch fine on OSX.4 on PPC G4. I do have a couple
> random things which came out of it, but I assume these are known -
> just in case, I post them:
>
> 1. I get this error message during the Sphinx run:
>
> docstring of
> sage.schemes.e
On Apr 26, 6:48 am, David Joyner wrote:
> Hi:
>
> I upgraded my phemon chip box to amd64 ubuntu 9.04 (jaunty jackalope)
> from 8.10. This is a brief report of its effect on Sage.
>
> The upgrade took 12 hours.
I assume you mean the Ubunu update?
> The Sage binaries for 8.10 seem to
> run with
On Apr 26, 11:50 am, Tim Abbott wrote:
> On Sun, 26 Apr 2009, mabshoff wrote:
> > Well, I am not 100% sure Sage will pass doctests with Python 2.6. I
> > know that at leasy NetworkX does not work with Python 2.6 according to
> > the author. Did you try to run docte
On Apr 26, 11:53 am, David Joyner wrote:
> On Sun, Apr 26, 2009 at 2:42 PM, mabshoff wrote:
> > Well, I am not 100% sure Sage will pass doctests with Python 2.6. I
> > know that at leasy NetworkX does not work with Python 2.6 according to
> > the author. Did yo
On Apr 26, 2:31 pm, Fidel wrote:
> Hello!
Hi Fidel,
> I'm running Sage Version 3.4, Release Date: 2009-03-11.
>
> I get some kind of error when I execute the comamnd
>
> sage: CompleteGraph(2).show()
>
> I get an error message starting with
>
> libpng error: Image width or height is zero in
On Apr 26, 7:50 pm, jjoonathan wrote:
Hi,
> Sage fails to build under Darwin 10 (Mac OS X "Snow Leopard") because
> of a few small bugs in several of the packages. Here are the fixes,
> sorry if someone has posted these before, but it would be nice if the
> 3.4.1 tarball built out of the box
On Apr 26, 10:15 pm, jjoonathan wrote:
> On Apr 26, 9:49 pm, "Justin C. Walker" wrote:> I think you
> are violating your NDA with Apple.
Hi,
> I think the only detail I revealed that actually belongs to apple is
> the version number of darwin 10 (and possibly a "version range" of
> gcc). Si
On Apr 26, 10:31 pm, mabshoff wrote:
> On Apr 26, 10:15 pm, jjoonathan wrote:
Ahh - too many double negatives - my apologies for the double mail,
but again for the record:
> Well, neither 3.4.2 nor any subsequent release won't officially
won't -> will
> support a
complain bitterly when started).
>
> Weird.
Some 2.x releases were build with gcc 4.0.4 since they added C++ code
that does currently not work with gcc 4.2.4 for example. So run
mabsh...@sage:/disk/scratch/mabshoff-sage-releases/tools$ pwd
/disk/scratch/mabshoff-sage-releases/tools
mabsh...@sage
On Apr 27, 1:14 pm, rjf wrote:
Hi,
> The note about OpenModelica brought this to mind.
>
> Maxima is licensed under GPL, but it too has additional restrictions.
> You can see the original letter releasing the code to Bill Schelter
> from the DOE, whose people perhaps did not understand GPL
>
> Well, IANAL. Looking at COPYING in Maxima's source distribution it
> says:
>
> [quote]
> Maxima is dedicated to the memory of William F. Schelter. On 6 October
> 1998 William F. Schelter was formally notified that he could
> distribute
> DOE-MACSYMA upon terms of his choosing, in particular t
On Apr 27, 2:15 pm, Mike Hansen wrote:
> On Mon, Apr 27, 2009 at 2:02 PM, mabshoff wrote:
> > I have been looking athttp://www.gnu.org/licenses/gpl-faq.html, but
> > there are various questions and answers about "additional
> > permissions" , but nothing
On Apr 28, 12:45 am, "Dr. David Kirkby"
wrote:
> I'm not sure if this is Solaris specific or not, but I noticed that
> there are complaints about the use of 'deprecated or antiquated header'
> files in polybori.
It is not Solaris specific and will be fixed in the next PolyBoRi
release.
Cheers
On Apr 28, 7:23 pm, kcrisman wrote:
> > Is it just me?
>
> No, I get the same thing right now.
>
> - kcrisman
Fixed. Some partition run out of space :(
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To un
On Apr 28, 6:53 pm, William Stein wrote:
> Hi,
>
> Our goals for Sage-4.0, in order, are:
>
> 1. Switch from Maxima to Pynac for Symbolics.
> 2. Get doctest coverage for the core Sage library to 75%.
> 3. Official 32-bit Solaris support
> 4. OS X 64-bit.
>
> The top priority items on the TODO l
Hello folks,
3.4.1.rc0 ought to drop in the next 18 hours, so if you want something
in and still need it reviewed you ought to hurry up.
Once rc0 is done only essential bugfixes will be merged since we want
the release to be done by the end of this months ;)
Cheers,
Michael
--~--~-~--~
On Apr 28, 12:04 am, "Dr. David Kirkby"
wrote:
Hi David,
> Looking at the top level README.txt in sage-3.4.2.alpha0, there are a
> couple of things about Solaris of note. The first is minor - the second
> less so.
>
> 1) At one point its called Solaris, and another SOLARIS. After finding
> 'S
On Apr 28, 9:06 pm, Gonzalo Tornaria wrote:
> On Wed, Apr 29, 2009 at 12:41 AM, mabshoff wrote:
> >> 5. Switch from Clisp to ECL:
> >> http://trac.sagemath.org/sage_trac/ticket/5929
Hi,
> > Yeah, the main issue is not so much getting ecl and then Ma
On Apr 28, 9:04 pm, Alex Ghitza wrote:
> On Wed, Apr 29, 2009 at 1:44 PM, mabshoff wrote:
>
> > Hello folks,
>
> > 3.4.1.rc0 ought to drop in the next 18 hours, so if you want something
> > in and still need it reviewed you ought to hurry up.
>
> Assuming that
On Apr 29, 4:03 am, Martin Albrecht
wrote:
> > 4. Libsingular is completely broken on 64-bit OS X. Everybody who has
> > looked at this (me included) is currently stumped. Martin Albrecht hasn't
> > tried yet.http://trac.sagemath.org/sage_trac/ticket/5862
>
> I will try to see to it before
On Apr 30, 1:06 am, Simon King wrote:
> Dear developers,
>
> I am about to create an spkg which I hope may be optional one day. Its
> purpose is the computation of modular cohomology rings of finite p-
> groups (and may also include a database of the results for many
> groups, but first I want
o misc.o
calcSVD.o slInit_Sta
tic.o mpsr_Put.o mpsr_PutPoly.o mpsr_GetPoly.o mpsr_sl.o mpsr_Get.o
mpsr_GetMisc.o mpsr_Error.o ndbm.o sing_dbm.o -L../kernel -lkernel -L/
home/mabshoff/b
uild-3.4.1.rc4/sage-3.4.1.rc4-fulvia-gcc-4.3.3/local/lib -lnsl -
lsocket -lm -lsingfac -lsingcf -lntl -lgmp -lreadline -l
s own spkg. We
will discuss what to do with the DSage codebase at SD15 I assume.
The source tarball, upgrade bits as well as a sage.math binary are in
the usual place at
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.2/
I have done some preliminary build testing and it s
On Apr 25, 8:39 am, "Nicolas M. Thiery"
wrote:
Hi Nicolas,
> Before posting the patch to trac, I'll split it up into:
>
> - patch with all trivial import updates (the most invasive one)
> - main patch with the category framework (with updates to
> parents/morphism/...)
> and the categ
; But please: *keep me updated about any such change as soon as
> > possible* so as to limit conflicts. Every late conflict resolution
> > just delays even further the final merge.
>
> Seehttp://trac.sagemath.org/sage_trac/ticket/5887
>
You can always grep for filenames in ~mabshoff/r
On Apr 30, 3:54 pm, Kevin Horton wrote:
> sage 3.4.2-rc0 fails to install for me on a unbuntu 8.10 VM, failing
> with:
> cp: cannot create regular file `src/Lib/ctypes/__init__.py': No such
> file or directory
> Error copying patched ctypes
If I would have to guess the tarball is corrup
On Apr 30, 5:27 pm, Kevin Horton wrote:
> On 30 Apr 2009, at 20:15, Mike Hansen wrote:
>
> >> Stupid question - why does sage use uncompressed tarballs, instead of
> >> something like .tgz. I think a corrupted .tgz couldn't be expanded,
> >> and they would download quicker too.
>
> > Almost ev
On Apr 30, 5:56 pm, Kevin Horton wrote:
> On 30 Apr 2009, at 20:40, mabshoff wrote:
> > Tar has a verify option, so you might want to use that when
> > compilation attempts fail.
>
> man tar seems to say that the verify option is only available when
> creating tar
On Apr 30, 8:21 pm, John H Palmieri wrote:
> On Apr 30, 5:23 am, mabshoff wrote:
>
Hi John,
> Mac OS X 10.5, Intel: on an upgraded version, I had one doctest
> failure,
>
> sage -t "devel/sage/s
Van Nguyen
While playing around with this I came across this strangeness:
sage: q = var("q")
sage: f(q) = (q^4 - q^2 + 1) * (q^4 + q^3 + q^2 + q + 1) * (q^4 - q^3
: )
---
RuntimeError
On Apr 30, 9:47 pm, Robert Bradshaw
wrote:
> On Apr 30, 2009, at 9:41 PM, mabshoff wrote:
> > please open a ticket. I think you might be using figsize wrong, i.e.
> > it isn't supposed to be a list or at least it isn't in MPL. If I pass
> > figsize=2 in f
On Apr 30, 9:52 pm, Robert Bradshaw
wrote:
> On Apr 28, 2009, at 9:35 PM, mabshoff wrote:
> > Yep. Small, localized fixes is exactly what we want at this stage :)
>
> If you like pretty pictures, #5767 adds a lot of doctests to 3d
> plotting, and fixes some minor, s
On Apr 30, 10:06 pm, John H Palmieri wrote:
> On Apr 30, 8:54 pm, mabshoff wrote:
> > Is this reproducible?
>
> Apparently not: I've been trying to get it again, but unsuccessfully.
Yeah, my experience is that that code is inherently racy and no one
has even been abl
On Apr 30, 9:55 pm, Minh Nguyen wrote:
> Hi Michael,
Hi Minh,
> > please open a ticket. I think you might be using figsize wrong, i.e.
> > it isn't supposed to be a list or at least it isn't in MPL.
>
> If I do p.show(figsize=[500,500]) then *boom* and I know I'm doing
> something wrong as
On Apr 30, 11:38 pm, David Roe wrote:
> Hey all,
> There's a set of patches needing review. It brings doctest coverage of the
> p-adics folder from 28.3% to 100%, restructures the files so that the
> directory is less cluttered, deletes a number of files (some due to the
> restructuring, some
On Apr 30, 10:19 pm, William Stein wrote:
> On Thu, Apr 30, 2009 at 10:15 PM, mabshoff wrote:
> > I think figsize is meant as a scaling factor since otherwise there is
> > no way you can exceed 2^15 as a limit of the png size :)
>
> I think figsize is the width and
On May 1, 12:05 am, Jaap Spies wrote:
> Jaap Spies wrote:
> > mabshoff wrote:
> >> Hello folks,
>
> > Now doing a fresh install on this machine.
Hi Jaap,
> On this fresh install first success, followed by the failure:
>
> SAGE build/upgrade complete!
>
On May 1, 1:26 am, "Dr. David Kirkby" wrote:
> mabshoff wrote:
\
> Hi,
>
> I removed ncurses and Singular did build. BUT, I am a bit puzzled, as
> even before doing this, it appeared the Sage build failed at some other
> point (forget which, but I'm n
On May 1, 1:29 am, "Dr. David Kirkby" wrote:
> I have a couple of questions about the spkg files. I assume this is
> documented somewhere, and I'm sure I've been told before, but I can't
> find the posts.
>
> 1) In what order are the spgk files built? I assume there is a file
> somewhere which
On May 1, 1:53 am, "Dr. David Kirkby" wrote:
> Somewhat confused by the way Sage appeared to have failed at two
> different points before, I decided to delete all the sage directory
> and start again. This time, the Solaris tool chain had the right paths
> in before I started.
> clisp fails
On May 1, 12:13 am, mabshoff wrote:
> On May 1, 12:05 am, Jaap Spies wrote:
> > SAGE build/upgrade complete!
> > [j...@paix sage-3.4.2.rc0]$ ./sage -t
> > "devel/sage/sage/matrix/matrix_symbolic_dense.pyx"
> > sage -t "devel/
On May 1, 2:36 am, "Dr. David Kirkby" wrote:
> mabshoff wrote:
> > Any clisp release I ever tried to build on Sparc is basically broken
> > with anything later than gcc 3.2.3. There was a thread on clisp-devel
> > about this and it boils down to tthe following:
On May 1, 6:54 am, Kiran Kedlaya wrote:
> Clean build on 64-bit Fedora 10 (Opteron) fails one doctest:
Hi Kiran,
> sage -t "devel/sage/sage/sets/primes.py"
> **
> File "/opt/sage/sage-3.4.2.rc0/devel/sage/sage/sets/primes.py
On May 1, 5:25 am, Alex Ghitza wrote:
> For the record, I'm also getting this on an older laptop running
> 32-bit arch linux.
Thanks, I have seen this no on Linux for x86, x86-64 as well as
Itanium, so we ought to get a handle on this today. It is now #5957.
> Alex
Cheers,
Michael
--~--~---
On May 1, 7:38 am, kcrisman wrote:
> > > sage: P>x^2+x
> > > Expected:
> > > True
> > > Got:
> > > False
>
> Yes, I just added that test to show that Primes() has comparison. I
> was a little surprised to see the result, but it passed testing, so...
>
> If someone posts a ticket wi
On May 1, 7:32 pm, Prabhu Ramachandran wrote:
> Dear Sage developers,
Hi Prabhu,
> I tried to build Sage-3.4 on my intel macbook (Mac OS X 10.4.11). I
> have Xcode 2.5 installed and gcc-4.0.1. I downloaded the sage-3.4.tar,
> untarred it and ran make. I have macports installed so changed the
On May 2, 1:25 am, Prabhu Ramachandran wrote:
> mabshoff wrote:
> >> I think this should be documented somewhere so others don't fall into
> >> the same trap. Thanks.
Hi,
> > Cool. Thanks for telling us - I have made this #5961.
>
> Glad to be of some
On May 2, 2:58 am, Alex Ghitza wrote:
> On Fri, May 1, 2009 at 5:13 PM, mabshoff wrote:
>
> > While going over the open tickets in 4.0 I noticed this ticket:
>
> > #5943 (Sage 3.4.2.a0: prime_pi(2^50) segfaults)
>
> > If someone could take a stab at that
On May 2, 1:00 pm, mabshoff wrote:
> On May 2, 2:58 am, Alex Ghitza wrote:
> > I played around with prime_pi() for a while, both on sage.math and on
> > my laptop at the office (macbook running 32-bit archlinux). I didn't
> > manage to get a segfault on either
On May 2, 2:44 pm, "Dr. David Kirkby" wrote:
> Alex Ghitza wrote:
Hi David,
> > I'm pretty sure that the sage.math answer is more likely to be the
> > right one. You can maybe guess from the timings why I didn't try
> > prime_pi(2^51). I have, however, tried smaller values. I'm going to
On May 2, 3:52 pm, William Stein wrote:
> On Sat, May 2, 2009 at 2:50 PM, mabshoff wrote:
> > The suggestion then was to implement something on top of the range
> > computed with floats using MPFR for example, but we will see what
> > happens. I am sure that if I asked
On May 1, 6:54 am, Kiran Kedlaya wrote:
> Clean build on 64-bit Fedora 10 (Opteron) fails one doctest:
>
> sage -t "devel/sage/sage/sets/primes.py"
> **
> File "/opt/sage/sage-3.4.2.rc0/devel/sage/sage/sets/primes.py", line
>
On May 2, 6:39 pm, kcrisman wrote:
> > For the record: This is now #5966 and will be fixed in 3.4.2.final.
>
> It also has been #5959, with a patch, since yesterday morning -
> figured if I caused the trouble, I should fix it :) That doesn't
> address "needlessly starting Maxima" but unfortuna
Ok, I would suggest we do the following:
* In 3.4.2 cap prime_pi at 2^40 since that is what Andrew suggests as
correct range for his algorithm
* add the following #long doctest (it takes about 25 seconds total in
sage.math):
sage: for n in (30..40):
: time prime_pi(2^n)
* For the r
On May 3, 3:07 am, jyr wrote:
> Hi,
Hi Jens,
> I have coded some routines that calculate Wigner 3j, 6j, 9j, Clebsch-
> Gordan, Racah and Gaunt coefficients (integrals over 3 spherical
> harmonics) exactly. It is all in a single python file with doc tests.
> If I am not mistaken then Sage curr
On May 3, 6:48 pm, "brandon.bar...@gmail.com"
wrote:
> Hello,
Hi,
> I'm very happy about the improved Solaris support. Until recently I
> was running sage in a linux zone on my workstation, but unfortunately
> modern linux version support for branded zones is lagging. I confess
> I've also
On May 3, 7:14 pm, bbarker wrote:
> Hi Michael,
Hi Brandon,
> 1 and 2 are both outside of zones (they are in the "global zone"), and
> they also hang seemingly indefinitely (I haven't kept them running
> long enough to prove me wrong yet, other than the one running in the
> zone).
Well, it s
Hello folks,
we are missing 4 rather easy reviews for 3.4.2.final. The main problem
has been fixed, reviewed and merged, i.e. the Maxima related doctest
failure, so now we need to have reviews for the tickets at
http://trac.sagemath.org/sage_trac/query?status=assigned&status=new&status=reope
On May 3, 7:36 pm, bbarker wrote:
> Some additional information:
>
> Trying to exit the server during hang by pressing Ctrl-C repeatedly
> will only yield the following (repeatedly):
> ^Cselect() error: Interrupted system call
> ^Cselect() error: Interrupted system call
> ^Cselect() error: Inte
On May 3, 5:54 am, "Dr. David Kirkby" wrote:
> mabshoff wrote:
> > Ok, I would suggest we do the following:
>
> > * In 3.4.2 cap prime_pi at 2^40 since that is what Andrew suggests as
> > correct range for his algorithm
> > * add the following #long
On May 3, 5:54 am, "Dr. David Kirkby" wrote:
> mabshoff wrote:
Sorry, I forgot to reply to this part of the post since I thought it
was in another independent post.
> > * For the range of 2^40+1 to 2^46 I am uncomfortable to have it
> > available per default,
Hello folks,
the final release for 3.4.2 is done and sources, the upgrade bits and
a sage.math binary are in the usual place at
http://sage.math.washington.edu/home/mabshoff/release-cycles-3.4.2/
I was cocky and labeled the release 3.4.2 instead of 3.4.2.final since
I am pretty confident we
On May 4, 7:57 am, Jaap Spies wrote:
> mabshoff wrote:
> > Well, I knew FLINT still ran its test suite and given we updated MPIR
> > I do prefer for it to run. There was also no 3.4.2 ticket to turn it
> > off :p.
>
> This testing feels ok for alpha and rc r
On May 4, 5:52 am, Minh Nguyen wrote:
> Hi folks,
>
> Sage 3.4.2 is basically done by now. So if you contributed some cool
> features to that release, you're invited to showcase those features on
> the release tour at
>
> http://wiki.sagemath.org/sage-3.4.2
>
> Of course, you're welcome to add
On May 4, 7:40 am, William Stein wrote:
> On Mon, May 4, 2009 at 7:36 AM, mabshoff wrote:
>
> > On May 4, 7:30 am, Jaap Spies wrote:
> >> mabshoff wrote:
> >> > Hello folks,
>
> >> > the final release for 3.4.2 is done and sources, the upgra
On May 4, 8:26 am, Jaap Spies wrote:
> > Nope, it was commonly handled that way. But since the 'real' releases
> > are build more widely that either alpha or rc releases I have been
> > changing this to even run some test suites even then. This has already
> > flushed out various bugs in MPI
On May 4, 7:30 am, Jaap Spies wrote:
> mabshoff wrote:
> > Hello folks,
>
> > the final release for 3.4.2 is done and sources, the upgrade bits and
> > a sage.math binary are in the usual place at
>
> > http://sage.math.washington.edu/home/mabshoff/release-cy
On May 4, 5:53 am, mabshoff wrote:
> Hello folks,
> #5957: Michael Abshoff: 3.4.2.rc0: Maxima related doctest failure in
> matrix/matrix_symbolic_dense.pyx [Reviewed by Michael Abshoff]
Oops, author credit here goes to William. I uploaded the patch, so
that caused the confusi
On May 4, 9:07 am, Jaap Spies wrote:
> mabshoff wrote:
> > Hello folks,
> > Please build, test and report issues as usual.
>
> On Fedora 9, 32 bit upgraded from alpha0 -> rc0-> sage-3.4.2
> and on Fedora 10, 32 bit upgraded from rc0 I get tons
> of failures
On May 4, 9:33 am, mabshoff wrote:
> On May 4, 9:07 am, Jaap Spies wrote:
> Arrg, this is cause by Integer(2**40) on 32 bit systems being "0" in
> Cython. I didn't use any long representation of 2^40 to avoid running
> into 32 vs. 64 bit issues. Oh well, pl
1801 - 1900 of 2912 matches
Mail list logo
