On 12/11/2010 07:18 AM, Jeroen Demeyer wrote:
> On 2010-12-11 14:10, G Hahn wrote:
>> Thanks for the link and your help! If avoiding the preparser just
>> consists in putting a "%python" in the first line and starting the
>> timing from another cell, then I already did that. But still the
>> notebo
On 12/05/2010 08:28 AM, Jeroen Demeyer wrote:
> It seems that sage -f sagenb-VERSION doesn't actually do anything. It
> does NOT change the devel/sagenb-main directory. This issue also breaks
> upgrading sage-4.6 to sage-4.6.1.alpha3 for me, because sagenb is not
> actually upgraded. Either I'm
On 12/05/2010 06:38 PM, Maxim wrote:
> I would like to know if it could be considered to add a feature that
> would allow one to disable spell-checking inside a worksheet. I often
> find my code all underlined in red, and need to disable spell-checking
> for every code block that I create (it's on
On 11/30/2010 02:49 AM, John Cremona wrote:
> On Mon, Nov 29, 2010 at 11:50 PM, John H Palmieri
> wrote:
>> On Nov 29, 2:24 pm, Niles wrote:
>>> On Nov 29, 9:11 am, John Cremona wrote:
>>>
Can anyone tell me how to make just part of the pdf reference manual,
specifically the part from
Thanks to everyone for their suggestions! I'll try to implement (or
start implementing) them soon.
--
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 a
On 11/24/2010 03:52 PM, David Kirkby wrote:
> On 24 November 2010 20:07, William Stein wrote:
>> On Wed, Nov 24, 2010 at 10:22 AM, David Kirkby
>> wrote:
>>> I copied a complete file system containing my home directory (and so a
>>> build of Sage) from one machine to another. I then run all the
On 11/16/2010 02:19 PM, Vincent D wrote:
> The problem may come from incompatibility between mercurial on my
> laptop (hg 1.3.1 distributed with Sage) and mercurial on the server at
> combinat.sagemath.org. Does anybody knows its version (or how obtain
> it) ?
I see
s...@sagemath:~$ which hg
/usr
On 11/15/2010 08:54 PM, François Bissey wrote:
> Ross Kyprianou wrote:
>> Thought you might like to know that sage-4.6.1.alpha1 built with no
>> probs but
>> alpha2 failed to build on Ubuntu 10.10 (linux 2.6.35-23-generic)
>> (PC = 2GB Ram, Intel Pentium 4 CPU 3.2GHz)
>>
>> Error was...
>> make[2]:
On 11/15/2010 07:55 PM, Dr. David Kirkby wrote:
> Thank you John. I forgot that had been fixed. I noticed that the
> buildbot failed on t2 to build a binary
Are you referring to fulvia's binary builder 'SunOS 5.10-32 bin
(fulvia)'? This fails to build ATLAS with SAGE_FAT_BINARY=yes. Do you
have
On 11/09/2010 04:34 AM, David Kirkby wrote:
> On 9 November 2010 10:21, Mitesh Patel wrote:
>> I've added './sage -startuptime', './sage -coverageall', PEP 8 [1,2]
>> style, and PyFlakes [3] steps to the buildbot's 'sage' bu
I've added './sage -startuptime', './sage -coverageall', PEP 8 [1,2]
style, and PyFlakes [3] steps to the buildbot's 'sage' builder. Here's
a report for 4.6.1.alpha0:
http://build.sagemath.org/sage/builders/sage/builds/94
Feel free to make suggestions!
[1] http://www.python.org/dev/peps/pep-000
Running 'hg verify' in 4.6.1.alpha0's sage repository, I see
$ cd SAGE_ROOT/devel/sage
$ hg verify
checking changesets
checking manifests
crosschecking files in changesets and manifests
checking files
data/.gitignor...@10122: missing revlog!
data/.hgignor...@0: missing revlog!
[...]
data/spkg-i
On 11/05/2010 07:25 PM, Jason Grout wrote:
> On 11/5/10 5:16 PM, Mitesh Patel wrote:
>> On 11/05/2010 07:49 AM, kcrisman wrote:
>>>
>>>> http://sage.math.washington.edu/home/buildbot/binaries/
>>>>
>>>> Does it usually take a long time (~1 hour
On 11/05/2010 10:19 PM, Robert Bradshaw wrote:
> On Fri, Nov 5, 2010 at 6:12 PM, Martin Albrecht
> wrote:
>> in the Sage library we cannot write the following C++ code:
>>
>> Class a = Class()
>>
>> since Cython turns the statement
>>
>> cdef Class a = Class()
>>
>> into
>>
>> Class a
>> a = C
On 11/05/2010 07:49 AM, kcrisman wrote:
>
>> http://sage.math.washington.edu/home/buildbot/binaries/
>>
>> Does it usually take a long time (~1 hour) to make a dmg distribution on
>> bsd.math, or more generally, on OS X?
>
> It can take quite a while on a slower machine; I feel like bsd.math is
>
On 11/01/2010 05:26 PM, David Kirkby wrote:
> On 1 November 2010 22:23, Jeroen Demeyer wrote:
>> On 2010-11-01 22:59, Mitesh Patel wrote:
>>> By the way, what is the best way to copy an entire [scratch-built] Sage
>>> distribution on Solaris? For example,
>>>
On 11/05/2010 03:05 AM, Dr. David Kirkby wrote:
> On 11/ 5/10 07:41 AM, Mitesh Patel wrote:
>> On 11/05/2010 02:26 AM, Dr. David Kirkby wrote:
>>> I see this with 4.6 and 4.6.1.alpha0
>>>
>>> drkir...@hawk:~/sage-4.6$ grep WARN docpdf.log
>>> writin
On 11/05/2010 02:26 AM, Dr. David Kirkby wrote:
> I see this with 4.6 and 4.6.1.alpha0
>
> drkir...@hawk:~/sage-4.6$ grep WARN docpdf.log
> writing...
> /export/home/drkirkby/sage-4.6/devel/sage/doc/en/faq/faq-usage.rst::
> WARNING: unusable reference target found: about:plugins
> writing...
> /ex
On 11/03/2010 12:29 AM, Bill Hart wrote:
> I've been down with the flu for a few days and so amusing myself in
> ways that don't make my head hurt too much. So, for fun, I just read
I hope you get better soon!
> through the *very* long trac ticket for getting the new Pari into
> Sage.
>
> Firstl
Here are a few potentially useful talks on APIs and testing:
How To Design A Good API and Why it Matters
Joshua Bloch
http://www.youtube.com/watch?v=aAb7hSCtvGw
Slides: http://lcsd05.cs.tamu.edu/slides/keynote.pdf
Competing On The Basis Of Speed
Mary Poppendieck
http://www.youtube.com/watch?v=U%5
On 11/01/2010 04:03 PM, David Kirkby wrote:
> The buildbot
>
> http://build.sagemath.org/sage/waterfall
>
> seems to be doing a good job of testing a specific revision of Sage.
>
> But looking at some of the bug reports, they seem to be related to
> upgrading Sage from version n to n+1. Would it
On 10/31/2010 04:52 AM, David Kirkby wrote:
> On 31 October 2010 00:09, David Kirkby wrote:
>
>> So far all passes of 1202 runs on OpenSolaris.
>>
>> This is with very latest alpha I managed to find (sage-4.6.1.alpha0).
>> I'll try it with 4.6.rc0 too.
>>
>> Dave
>>
>
> I got a number of failure
On 10/30/2010 06:09 PM, David Kirkby wrote:
> On 30 October 2010 23:55, Mitesh Patel wrote:
>> On 10/30/2010 05:35 PM, David Kirkby wrote:
>>> On 30 October 2010 23:14, Mitesh Patel wrote:
>>>> I ran
>>>>
>>>> ./sage -t -long -force_lib "
On 10/27/2010 08:26 PM, Mitesh Patel wrote:
> On 10/27/2010 08:43 AM, Dr. David Kirkby wrote:
>> 1) Despite previously claiming in README.txt that we supported Fedora
>> 32-bit on x86, the only host with Fedora 32-bit,
>>
>> http://build.sagemath.org/sage/buildslaves/cic
On 10/30/2010 05:35 PM, David Kirkby wrote:
> On 30 October 2010 23:14, Mitesh Patel wrote:
>> I ran
>>
>> ./sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
>>
>> 1000 times in serial [1] with a 64-bit 4.6.rc0 built on OS X 10.6
>>
I ran
./sage -t -long -force_lib "devel/sage/sage/libs/fplll/fplll.pyx"
1000 times in serial [1] with a 64-bit 4.6.rc0 built on OS X 10.6
(bsd.math). All but one of the runs pass. The failure:
Run 766 of 1000
Detected SAGE64 flag
Building Sage on OS X in 64-bit mode
sage -t -long -force_lib "d
On 10/29/2010 09:08 PM, David Kirkby wrote:
> On 30 October 2010 02:22, William Stein wrote:
>> Hi Sage-Devel,
>> I'm curious if people are getting emails like this...
>> (I don't have anything to do with this PacktPub project. Generally, I think
>> it is best for people to write documentation fo
On 10/27/2010 08:43 AM, Dr. David Kirkby wrote:
> 1) Despite previously claiming in README.txt that we supported Fedora
> 32-bit on x86, the only host with Fedora 32-bit,
>
> http://build.sagemath.org/sage/buildslaves/cicero-1
>
> has never had a successful build and test.
>
> 2) Despite previou
On 10/27/2010 02:36 AM, Robert Bradshaw wrote:
> On Wed, Oct 27, 2010 at 12:31 AM, Minh Nguyen wrote:
>> It would be interesting to see how line-by-line
>> annotation in code review works out in the long term.
>
> I can say from first hand experience, it works well.
Are you referring to a system
On 10/25/2010 05:04 PM, Dr. David Kirkby wrote:
> On 10/25/10 06:21 PM, kcrisman wrote:
2. what is needed to run a buildbot?
>>>
>>> Mitesh will know more, since he has set them up.
>>>
>>> I know for me personally I just gave him an account (username
>>> buildbot), and an IP address into whic
On 10/25/2010 11:55 AM, David Kirkby wrote:
> On 25 October 2010 17:26, Gonzalo Tornaria wrote:
>> On Mon, Oct 25, 2010 at 12:09 PM, David Kirkby
>> wrote:
>>> Since Minh has been using an external server (I think run by GNU) for
>>> Debian, we can probably add Debian at some point if we can get
On 10/25/2010 01:54 PM, William Stein wrote:
>> Also, I was talking to Craig Citro about this and he had the
>> interesting idea of creating some kind of a "test object" which would
>> be saved and then could be run into future versions of Sage and re-run
>> in. The idea of saving the tests that ar
On Sun, Oct 17, 2010 at 07:16:58PM +0200, Jeroen Demeyer wrote:
> r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard#env SAGE_CHECK=yes
> sage -f pari-2.3.5.p4.spkg
> Force installing pari-2.3.5.p4.spkg
> ...
> Finished installing pari-2.3.5.p4.spkg
> r...@capepoint:/usr/local/src/sage-4.5.3/
On 10/22/2010 12:12 PM, kcrisman wrote:
> On Oct 22, 1:08 pm, Mike Hansen wrote:
>> On Fri, Oct 22, 2010 at 8:47 AM, kcrisman wrote:
>>> So somehow that isn't getting through. I may not have time to look
>>> into this for a while otherwise, so if no one else responds relatively
>>> soon feel fre
Are there accepted idioms for writing parallel code in Cython for the
Sage library? I don't yet have a specific application in mind, but I'm
interested in learning from any examples.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an em
We still have 4 blocker tickets for Sage 4.6 that need work or review:
Another doctest failure in sage/graphs/graphs.py
http://trac.sagemath.org/sage_trac/ticket/10081
Doctest error in sage/schemes/generic/toric_divisor.py on OS X
http://trac.sagemath.org/sage_trac/ticket/9926
Doctest failure in
On 10/12/2010 10:31 AM, kcrisman wrote:
> On Oct 12, 11:29 am, maldun wrote:
>> Thanks for the quick response! I will update my sage on this computer
>> then =)
>
> You might want to wait until the "official" release of Sage 4.6, which
> should be imminent, rather than doing sage -upgrade, which
On 10/10/2010 11:54 AM, Jeroen Demeyer wrote:
> As part of the "rewrite interrupt handling" ticket #9678, I decided that
> _sig_on should be an *inline function* instead of a macro (one very good
> reason for this would be that we can declare it cdef inline int sig_on()
> except -1 in order to use
On 10/09/2010 04:55 AM, Dr. David Kirkby wrote:
> I've looked at the logs from the buildbot on sage.math and see that too
> reports to be using 12 jobs in parallel. Unless the makefile was edited
> (which I can't see, but doubt very much), the number of parallel should
> be limited to 8.
The curre
On 10/09/2010 06:41 AM, Minh Nguyen wrote:
> I built Sage 4.6.alpha3 from source on sage.math and wrapped up a
> binary distribution for that machine. I then unpacked the binary
> distribution and loaded Sage using that binary. This is what I get:
>
> [mv...@sage sage-4.6.alpha3-sage.math.washingt
Hi David,
I was "manually" testing #4000's Solaris GCC workaround against a trial
4.6.alpha3 compiled earlier by Buildbot. I can reduce the number of
test jobs. Just let me know.
Sincerely,
Mitesh
On 10/08/2010 04:12 AM, Dr. David Kirkby wrote:
> I've noticed my machine (which is a buildbot s
On 10/06/2010 03:21 PM, mhampton wrote:
> I am having trouble getting a wiki working with sage-4.6.alpha2. I
> have a feeling that not many people use the wiki command, so maybe it
> is not tested well. Can someone else check if it still works? I am
> wondering if it is specific to my setup or j
Is there a complete list of "active" public Sage mailing lists at
sagemath.org or the Sage wiki? I'm aware of
sage-algebra
http://groups.google.com/group/sage-algebra
sage-announce
http://groups.google.com/group/sage-announce
sage-combinat-devel
http://groups.google.com/group/sage-combinat-devel
On 10/02/2010 05:57 AM, Mitesh Patel wrote:
>> On 10/1/10, ancienthart wrote:
>>> I get the following:
>>>
>>> a = FFT(4)
>>> a[1] = 2
>>> a.forward_transform()
>>>
>>> Everything works fine up to here. Then, when I do this:
&g
On 10/02/2010 05:39 AM, Tom Boothby wrote:
> Was this on sagenb.org? Frequently, the server will kill your process
> at the most inopportune times...
>
> On 10/1/10, ancienthart wrote:
>> I get the following:
>>
>> a = FFT(4)
>> a[1] = 2
>> a.forward_transform()
>>
>> Everything works fine up to
On 09/29/2010 01:28 PM, kcrisman wrote:
> On Sep 29, 1:37 pm, Jason Grout wrote:
>> Is there a target date for the feature freeze? (I assume 4.6.alpha2?)
>
> This has been mentioned as the target on several Trac tickets, but not
> here.
>
>> I want to make sure that a couple of changes to sag
On 09/22/2010 02:43 PM, John Cremona wrote:
> Since the big Pari upgrade we have had this:
>
>
> j...@selmer%sage -q
> sage: version()
> 'Sage Version 4.6.alpha1, Release Date: 2010-09-18'
> sage:
> Exiting Sage (CPU time 0m0.07s, Wall time 0m5.56s).
> Exiting spawned GP/PARI interpreter process.
On 09/21/2010 07:57 AM, luisfe wrote:
> I have recently upgraded my "stable" version of sage to 4.5.3 from
> 4.51 using
> "sage -upgrade"
>
> I upgraded sage with a user called "Alice" having write and read
> access to the sources.
>
> I have another user "Bob" that can only read the sources and
On 09/20/2010 01:52 AM, Dr. David Kirkby wrote:
> On 09/20/10 07:44 AM, Johan S. R. Nielsen wrote:
>
>>> Just to check: What happens if you rerun these tests?
>>>
>>> $ cd SAGE_ROOT
>>> $ ./sage -t "devel/sage/sage/misc/explain_pickle.py"
>>> $ ./sage -t "devel/sage/sage/combinat/iet/reduced.py"
On 09/19/2010 08:45 PM, dmharvey wrote:
> On Sep 19, 9:28 pm, dmharvey wrote:
>> Curiouser and curiouser it has nothing to do with matrices. Even
>> doing this causes the problem:
>>
>> K = Integers(13^10)
>> M = [[K.random_element() for j in range(200)] for k in range(200)]
>> save(M, "thing.
On 09/18/2010 05:39 AM, Johan S. R. Nielsen wrote:
> I downloaded the Sage 4.5.3 source, compiled everything and ran a
> doctest (./sage -testall) immediately afterwards. I guess everything
> should run smoothly, but surprisingly, there were two failures:
>
> -
> sage -t "devel/sage/sage/misc
On 09/18/2010 02:10 PM, Robert Bradshaw wrote:
> On Sat, Sep 18, 2010 at 6:17 AM, Niles wrote:
>> but the test only runs on sage.math, so is it only a bug on
>> sage.math?
>
> Well, that was a lot easier than having some kind of system
> calibration in place for all other computers...
We *could*
On script portability:
Does anyone have experience with a script called 'checkbashisms'?
The rpmdevtools package on Fedora includes a version of this script.
The devscripts package includes it on Ubuntu, but the package is not
installed on the Sage cluster.
--
To post to this group, send an ema
On 09/17/2010 04:08 AM, Mike Hansen wrote:
> On Fri, Sep 17, 2010 at 12:12 AM, Jeroen Demeyer
> wrote:
>> I do not like the sage/tests/startup.py test (which tests, only on
>> sage.math.washington.edu, that Sage starts up in 1.5 seconds). I
>> regularly get non-reproducible failures in this doct
On 09/17/2010 02:25 AM, Dr. David Kirkby wrote:
> http://trac.sagemath.org/sage_trac/ticket/9733
>
> is supposed to fix "Parallel build of Singular 3-1-1-4-package fails in
> rare case"
>
> I just downloaded the sage-4.6.alpha1.tar file (Mihesh gave a hint where
> it was), and it failed on buildi
On 09/12/2010 10:19 PM, mda_ wrote:
> On Sep 12, 5:44 pm, Mitesh Patel wrote:
>> [...]
>> This appears to work:
>>
>> sage: bool(e^(-pi/2) == i^i)
>> True
>
> Thanks Mitesh. What is the sage convention for returning the object
> as a result of "=
On 09/13/2010 09:40 AM, Dr. David Kirkby wrote:
> 2) SAGE_FAT_BINARY=yes for *part* of the build. SAGE_FAT_BINARY screws
> up the ATLAS build, so perhaps it screws up something else.
The list of possible packages appears to include ATLAS, libm4ri, MPIR,
R, and their dependencies:
$ mkdir packages
On 09/12/2010 06:41 PM, mda_ wrote:
> sage: float(e^(-pi/2))
> 0.20787957635076193
>
> The last digit should be 1, since
> i^i = 0.20787957635076190854
You could try, e.g.,
sage: (e^(-pi/2)).numerical_approx(100)
0.20787957635076190854695561983
sage: (i^i).numerical_approx(100)
0.2078795
On 09/07/2010 06:03 PM, Dr. David Kirkby wrote:
> I decided to run "sage -upgrade" today - for about the first time ever.
> I'm going to try to upgrade sage-4.5.3.alpha2 to sage-4.5.3. I don't
> know if its a good idea to update alphas or not, but I'm not bothered if
> it fails or not.
>
>
> I ge
Minh Nguyen gets the error below on a GCC compile farm Debian 5.0
machine (gcc100.fsffrance.org, AMD Opteron(tm) Processor 252 @ 2647.708
MHz). Please see
http://trac.sagemath.org/sage_trac/ticket/9866
sage -t -long "devel/sage/sage/schemes/elliptic_curves/heegner.py"
Exception RuntimeError: R
On 08/24/2010 08:01 PM, William Stein wrote:
> On Tue, Aug 24, 2010 at 1:38 PM, William Stein wrote:
>> On Mon, Aug 23, 2010 at 8:25 PM, Jonathan Hanke wrote:
>>> Hi,
>>>
>>> I'm trying to build sage 4.5.2 on a Sun Fire X4450 server (Intel Xenon
>>> processors) running Redhat linux (Enterprise ed
On 09/05/2010 05:23 AM, David Kirkby wrote:
> On 5 September 2010 10:14, Mitesh Patel wrote:
>> On 09/05/2010 03:52 AM, David Kirkby wrote:
>>> I'm quite happy to be that someone who learns Lisp - I'm serious
>>> thinking of buying a book on it. Unfortunately
Hi David,
On 09/05/2010 03:52 AM, David Kirkby wrote:
> I'm quite happy to be that someone who learns Lisp - I'm serious
> thinking of buying a book on it. Unfortunately, they tend to be quite
> expensive, as do books on writing compilers.
Some time ago, I found "Practical Common Lisp" by P. Seib
On 09/02/2010 03:17 AM, Simon King wrote:
> On Sep 2, 12:42 am, Mitesh Patel wrote:
>> ...
>> If you still have a copy of the "hanging" package directory, could you
>> try print-debugging to isolate the problem? Possibilities include the
>> system calls to
Here's an interesting talk by Thomas Wouters on "Advanced Python (or
understanding Python)"
http://www.youtube.com/watch?v=E_kZDvwofHY
It's a few years old, but it could still be useful to intermediate
Python programmers.
--
To post to this group, send an email to sage-devel@googlegroups.com
To
On 09/01/2010 07:43 AM, Simon King wrote:
> When I tried to create an spkg out of a folder with many uncommitted
> changes in the mercurial repository, after a while the process hanged.
> It was invisible to "top" and didn't finish (I waited something like
> 10 minutes). But after committing the ch
On 09/01/2010 04:33 PM, Niles wrote:
> Over at asksage, I complained that the sage documentation bears no
> resemblance to sagemath.org, and I for one actually did find this a
> little confusing at first (until I realized that all python
> documentation looks like this, by default). That complaint
On 08/31/2010 04:49 PM, Niles wrote:
> I've noticed a separate list of developers on the DevMap at
> sagemath.org . . . is there a plan to integrate these two lists?
Harald, what do you think?
There are directions at the bottom of the world DevMap page for
submitting updates:
http://www.sagemath
If you're a Sage user-developer who has a Sage trac account, could you
check, update, and/or add your entry to
http://trac.sagemath.org/sage_trac/wiki/WikiStart#AccountNamesmappedtoRealNames
?
If you don't have an account, but you're thinking about contributing to
Sage, please sign up at
http:
On 08/27/2010 05:44 PM, Ryan Hinton wrote:
> Any guesses when the snazzy new Cython 0.13 will end up in Sage? I
I don't know, but I've opened
http://trac.sagemath.org/sage_trac/ticket/9828
> currently have some snazzy C++ code that I want to wrap in Cython
> (uses namespaces, etc.), and the new
On 08/26/2010 05:33 PM, maldun wrote:
> I have put the task on trac: http://trac.sagemath.org/sage_trac/ticket/9808
> I already can provide working packages for download.
> I host the files at megaupload, at: Numpy:
> http://www.megaupload.com/?d=6GCFZD65
> Scipy: http://www.megaupload.com/?d=JO
On 08/25/2010 07:08 PM, David Kirkby wrote:
> spkg/standard/deps shows:
>
> $(INST)/$(CLIQUER): $(BASE) $(INST)/$(SCONS)
> $(INSTALL) "$(SAGE_SPKG) $(CLIQUER) 2>&1" "tee -a
> $(SAGE_LOGS)/$(CLIQUER).log"
>
>
> but as far as I can tell, there is no such dependency.
>
> Cliquer is a stand
or linked to the ticket.
I've updated the ticket description with a link to the SPKG.
> On 23 August 2010 14:19, Mitesh Patel wrote:
>> Ticket #9722
>>
>> http://trac.sagemath.org/sage_trac/ticket/9722
>>
>> is a 4.5.3 blocker that awaits testing on various sys
Ticket #9722
http://trac.sagemath.org/sage_trac/ticket/9722
is a 4.5.3 blocker that awaits testing on various systems and a review.
The ticket fixes build problems with PARI 2.3.5. We'll need to port the
fixes to the newer PARI version at #9343.
I'd like to merge #9722 into 4.5.3.rc0 (which I
This is one of those messages that tries to 'raise Awareness'.
To run all of the optional doctests, regardless of their modifiers, we
can use
sage -t -only-optional
Most machines do not have all of the optional packages installed, so
it may be more useful to target a particular package:
sage -t
On 08/12/2010 05:01 PM, Mitesh Patel wrote:
> On 08/11/2010 07:19 PM, Robert Bradshaw wrote:
>> Thanks for looking into this, another data point is really helpful. I
>> put a vanilla Sage in hudson and for a while it was passing all of its
>> tests every time, then all of
We're currently planning to merge the big PARI upgrade tickets
http://trac.sagemath.org/sage_trac/ticket/9343
http://trac.sagemath.org/sage_trac/ticket/9591
http://trac.sagemath.org/sage_trac/ticket/9592
into 4.6.alpha0.
I'm planning to release Sage 4.5.3.rc0 by Monday, 23 August, and, if all
go
On 08/21/2010 02:12 AM, Jason Grout wrote:
> On 8/20/10 2:44 PM, Ryan Hinton wrote:
>> I have a build of Sage at school that I occasionally update when a bug
>> or upgrade affects me. I'm the only one who uses it, but it's
>> installed in a public location (i.e. not writable by me) in case
>> some
On 08/20/2010 02:55 AM, Dr. David Kirkby wrote:
> On 08/20/10 02:03 AM, Mitesh Patel wrote:
>> On 08/19/2010 12:16 PM, Dr. David Kirkby wrote:
>>> I am running some doc tests on my Blade 1000 and was concerned that the
>>> file ptestlong.log had not had the time sta
On 08/19/2010 12:16 PM, Dr. David Kirkby wrote:
> I am running some doc tests on my Blade 1000 and was concerned that the
> file ptestlong.log had not had the time stamp changed for over an hour.
>
> Using ls, I see:
>
> -rw-r--r-- 1 drkirkby other 190759 Aug 19 16:36 ptestlong.log
>
> but
On 08/18/2010 07:13 PM, William Stein wrote:
> On Wed, Aug 18, 2010 at 4:18 AM, David Kirkby wrote:
>> On 18 August 2010 11:33, John Cremona wrote:
>>> On 17 August 2010 23:31, William Stein wrote:
>>
>> It would be a student project to reimplement Mark W's algorithm (Here:
>> http://www
On 08/16/2010 05:26 PM, Richard wrote:
> I'd already posted this problem on the sage-support mailing list, but
> the issue could not be resolved. As it appears to be a bug, I am
> cross-posting to this list.
>
> [Please find the original thread on sage-support at
> https://groups.google.com/group/
William Stein or I wrote:
So sage-ptest may be responsible, somehow, for the faults that leave
cores in apparently random directories and perhaps also for random test
failures.
>>
>> Here's one problem: When we test
>>
>> /path/to/foo.py
>>
>> sage-doctest writes
>>
>> SAGE_TESTDIR/.
On 08/12/2010 05:18 PM, William Stein wrote:
> On Thu, Aug 12, 2010 at 3:01 PM, Mitesh Patel wrote:
>> I made 20 copies of 4.5.3.alpha0. In each copy, I ran the long doctest
>> suite serially with the alternate tester, which I modified to rename any
>> new cores after each
On 08/11/2010 07:19 PM, Robert Bradshaw wrote:
> On Wed, Aug 11, 2010 at 4:15 PM, Mitesh Patel wrote:
>> On 08/11/2010 03:25 AM, Mitesh Patel wrote:
>>> On 08/05/2010 11:12 PM, Robert Bradshaw wrote:
>>>> On Thu, Aug 5, 2010 at 4:26 AM, Mitesh Patel wrote:
>&g
On 08/11/2010 05:00 PM, William Stein wrote:
> On Wed, Aug 11, 2010 at 2:50 PM, Mitesh Patel wrote:
>> On 08/10/2010 04:35 AM, Kutoma Ltd wrote:
>>> Thanks for any clarification.Also maybe a other question.Is someone
>>> working on any Interop between Sage and Haskell.
On 08/11/2010 03:25 AM, Mitesh Patel wrote:
> On 08/05/2010 11:12 PM, Robert Bradshaw wrote:
>> On Thu, Aug 5, 2010 at 4:26 AM, Mitesh Patel wrote:
>>> On 08/04/2010 03:10 AM, Robert Bradshaw wrote:
>>>> So it looks like you're getting segfaults all over the pla
On 08/10/2010 04:35 AM, Kutoma Ltd wrote:
> Thanks for any clarification.Also maybe a other question.Is someone
> working on any Interop between Sage and Haskell.
I'm not aware of any ongoing projects to bridge Sage (or Python) and
Haskell. I'd be happy to be corrected!
I "found" this sage-devel
On 08/05/2010 11:12 PM, Robert Bradshaw wrote:
> On Thu, Aug 5, 2010 at 4:26 AM, Mitesh Patel wrote:
>> On 08/04/2010 03:10 AM, Robert Bradshaw wrote:
>>> On Sat, Jul 31, 2010 at 2:51 AM, Mitesh Patel wrote:
>>>> On 07/30/2010 01:54 AM, Craig Citro wrote:
>>
On 08/10/2010 12:23 PM, kcrisman wrote:
> Here is a ticket I hope we can close as invalid. I don't have that
> power, but it would be nice if a couple people could make sure this is
> true (esp. people who have lots of folders and files with non-ASCII
> names).It could be a really easy one to
* Mike Hansen
* Minh Van Nguyen
* Mitesh Patel
* Nathann Cohen
* Nicolas M. Thiéry
* Nils Bruin
* Ondrej Certik
* Oscar Gerardo Lazo Arjona
* Paul Zimmermann
* Radoslav Kirov
* Richard Lindner [first contribution]
* Rishikesh
* Rob Beezer
* Robert Bradshaw
* Robert Mařík
*
On 08/06/2010 04:41 AM, Simon King wrote:
> Let s be a string (e.g., a docstring containing tests). Is it possible
> to perform the analogue of "sage -t" on s without writing s into a
> file and running a sub-process "sage -t" on that file?
We're in the *very* early stages of developing a new doct
On 08/04/2010 03:10 AM, Robert Bradshaw wrote:
> On Sat, Jul 31, 2010 at 2:51 AM, Mitesh Patel wrote:
>> On 07/30/2010 01:54 AM, Craig Citro wrote:
>>> So we're currently working on a long-overdue release of Cython with
>>> all kinds of snazzy new features
On 08/03/2010 03:05 PM, Georg S. Weber wrote:
> On 3 Aug., 08:34, Rob Beezer wrote:
>> I just built a clone in about a minute. On a fresh install of
>> 4.5.2.rc0 created from source. Maybe with a binary install, the docs
>> need to be built on the first clone?
>
> No,
>
> the problem is with r
On 08/04/2010 08:14 PM, David Kirkby wrote:
> I'm building Sage on one of my SPARCs which does not have much RAM
> (only 2 GB), though its enough to build Sage OK. But I noticed when
> building the documenation, the memory usage is quite high.
>
> This is the output from 'prstat' - the Solaris too
On 08/02/2010 03:33 PM, John H Palmieri wrote:
>> I'm trying to reproduce this, but on skynet's taurus I don't even get a
>> liblapack.so, but only liblapack.a. (The build isn't done yet, but the lapack
>> package is done.)
>>
>> Am I missing something? I checked, but none of my recent sage builds
On 08/01/2010 05:23 PM, Mitesh Patel wrote:
> On 08/01/2010 12:06 PM, Dr. David Kirkby wrote:
>> Just to recap, my status for builds of Sage on Solaris are:
>>
>> * 32-bit SPARC on t2. Works perfect, though #9657 means Sage does not
>> build with gcc 4.5.0 and I doubt i
On 08/01/2010 12:06 PM, Dr. David Kirkby wrote:
> Just to recap, my status for builds of Sage on Solaris are:
>
> * 32-bit SPARC on t2. Works perfect, though #9657 means Sage does not
> build with gcc 4.5.0 and I doubt it will build with gcc 4.5.1. That's a
> very simple patch I'd like to get mer
On 07/30/2010 01:54 AM, Craig Citro wrote:
> So we're currently working on a long-overdue release of Cython with
> all kinds of snazzy new features. However, our automated testing
> system seems to keep turning up sporadic segfaults when running the
> sage doctest suite. This is obviously bad, but
On 07/31/2010 12:53 AM, Henryk Trappmann wrote:
> On Jul 29, 9:12 pm, kcrisman wrote:
>> I will point out, though, that you clearly *do* use Maxima, since you
>> tried to do this in Sage, which uses Maxima heavily.
>
> This may be, but I dont know about it.
> I know that Sage uses Maxima, but nei
1 - 100 of 104 matches
Mail list logo
