> Yes, the parallel build code was reworked for 4.0.1. Not sure why
> we're seeing this, but still.
>
Well, the parallel build code in 4.0.1 *should* be contained to the
sage build itself (it's in sage's setup.py, and it's a separate
builder that one has to instantiate). I won't say it's impossi
On 18-Jun-09, at 11:28 PM, gsw wrote:
>
>
>
> On 19 Jun., 08:21, gsw wrote:
>> Hi,
>>
>> r/rpy does not build reliably for me anymore using " export
>> MAKE='make
>> -j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this
>> already for Sage-4.0.2.rc0 (in a one-message thread :-) )
On 19 Jun., 08:21, gsw wrote:
> Hi,
>
> r/rpy does not build reliably for me anymore using " export MAKE='make
> -j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this
> already for Sage-4.0.2.rc0 (in a one-message thread :-) ) thinking
> that it would be sporadic, but it seems to h
Hi,
r/rpy does not build reliably for me anymore using " export MAKE='make
-j2' " on my MacIntel Core2Duo / Mac OS X 10.4.11. I reported this
already for Sage-4.0.2.rc0 (in a one-message thread :-) ) thinking
that it would be sporadic, but it seems to hit always now: I built
Sage-4.0.2.rc2 and Sa
I have not developed and tested a patch which allows ATLAS to build on
Solaris using gcc-4.4.0 on 't2'. Could someone please review please the
patch
http://trac.sagemath.org/sage_trac/ticket/6276
--~--~-~--~~~---~--~~
To post to this group, send email to sage-d
> All tests passed on 64-bit Ubuntu 9.04 and 32-bit Fedora 10. All tests
> passed on bsd.math, except that #6242 is still a problem; the
> birds_other.rst doctests segfault between a quarter and a third of the
> time.
>
Yep, this is a known issue. This is the same as #6304, which David
Harvey had
All tests passed on 64-bit Ubuntu 9.04 and 32-bit Fedora 10. All tests
passed on bsd.math, except that #6242 is still a problem; the
birds_other.rst doctests segfault between a quarter and a third of the
time.
Dan
--
--- Dan Drake
- KAIST Department of Mathematical Sciences
--- http:
Craig Citro wrote:
>> My most important debugging tool is logical deduction using my brain.
>>
>
> Someone want to open a trac ticket for including that in Sage? ;)
William's logical deductions are already progressively being included in
Sage!
--~--~-~--~~~---~--~
Hi all,
So everyone probably that we remembers that we won in the Science
category in the Trophees du Libre back in 2007. The 2009 awards have
been announced here:
http://www.trophees-du-libre.org/
Tim Abbott (who's the man behind sage being packaged for Debian) has
founded a startup called KSp
compiled fine and all tests passed on amd64 ubuntu 9.04.
On Thu, Jun 18, 2009 at 1:26 PM, Craig Citro wrote:
>
> Hi all,
>
> Here's rc3, which *should* be the last rc for this release cycle. I've
> tested it on my laptop and the build farm, and I've had no troubles at
> all, and it's currently
print ftw!
On Thu, Jun 18, 2009 at 10:50 AM, Carlo
Hamalainen wrote:
>
> Hi,
>
> I'm curious about which debugging environment is most popular among
> the Sage developers?
>
> * print statements only (ugh)
> * pdb
> * ddd
> * Eric4
> * something else?
>
> I just wrote a short post about how to ge
> My most important debugging tool is logical deduction using my brain.
>
Someone want to open a trac ticket for including that in Sage? ;)
-cc
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group,
Em Qui, 2009-06-18 às 20:41 +0200, William Stein escreveu:
>
> My most important debugging tool is logical deduction using my brain.
>
> -- William
Sounds very deep and witty. That's gotta become a quote on slashdot.
Ronan
--~--~-~--~~~---~--~~
To post to th
On Thu, Jun 18, 2009 at 09:20:56PM +0200, William Stein wrote:
> Of related interest, there are 8 publicly visible methods on SageObject:
>
> sage: s = SageObject()
> sage: s.
> s.categorys.db s.dumps.dumps s.rename
> s.reset_name s.saves.version
>
> I think I
All tests passed on a fresh build on ubuntu 32-bit (took no longer
than usual: 3099s).
Same on 64-bit (<3000s).
John
2009/6/18 Marshall Hampton :
>
> All tests passed on an intel mac pro running 10.4.11.
>
> The tests took 6975 seconds, which seems like a big increase from
> 3.0.2 (4818 seconds
All tests passed on an intel mac pro running 10.4.11.
The tests took 6975 seconds, which seems like a big increase from
3.0.2 (4818 seconds) and 3.4 (5358 seconds). Is this simply because
of the additional doctests, or are there serious speed regressions
somewhere? I recall some discussion abou
Jaap Spies wrote:
> Craig Citro wrote:
>> Hi all,
>>
>> Here's rc3, which *should* be the last rc for this release cycle. I've
>> tested it on my laptop and the build farm, and I've had no troubles at
>> all, and it's currently going on a few other machines, so hopefully
>> that'll turn out fine,
Nicole Jinn wrote:
> To whom it may concern,
>
> I was trying to install the package "mesa-7.2.spkg" and the following
> errors came up:
>
Note this is a very experimental package!
Only available in my home directory.
What are you trying to do?
Jaap
--~--~-~--~~~---
Hello,
On Thu, Jun 18, 2009 at 12:59 PM, Golam Mortuza Hossain
wrote:
>
> Hi,
> (1) Assumptions:
> How does the assumption framework work in new symbolic?
These are all done via Maxima.
>
> For example:
> --
> 1 > 0
> -
> True
> ---
> a=var('a');
> a > 0
> -
> a > 0
> ---
> assume(a>0)
>
To whom it may concern,
I was trying to install the package "mesa-7.2.spkg" and the following
errors came up:
GLwDrawA.c:48:28: error: X11/IntrinsicP.h: No such file or directory
GLwDrawA.c:49:28: error: X11/StringDefs.h: No such file or directory
In file included from GLwDrawAP.h:46,
On Jun 18, 12:17 pm, Jaap Spies wrote:
> Craig Citro wrote:
> > Hi all,
>
> > Here's rc3, which *should* be the last rc for this release cycle. I've
> > tested it on my laptop and the build farm, and I've had no troubles at
> > all, and it's currently going on a few other machines, so hopefully
>
Hi,
On Wed, Jun 17, 2009 at 8:56 AM, Burcin Erocal wrote:
> I don't know anyone working on this atm. You could do this as part of
> #2452 on trac. The example code I wrote for Maurizio is here:
>
> http://sage.math.washington.edu/home/burcin/pynac/dirac.py
>
> You probably need to put those evalf
On Thu, Jun 18, 2009 at 9:46 PM, Martin
Albrecht wrote:
>
>> * print statements only (ugh)
>
> I use it sometimes.
>
>> * pdb
>
> I use it mostly. Setting pdb.set_trace() sets a breakpoint from within the
> code.
>
If you type
sage: trace?
it has helpful documentation about pdb.set_trace(), in
> * print statements only (ugh)
I use it sometimes.
> * pdb
I use it mostly. Setting pdb.set_trace() sets a breakpoint from within the
code.
> * ddd
For some Cython stuff but mostly gdb directly.
> * Eric4
I used it a while ago: http://tinyurl.com/lxbk5h :)
> I just wrote a short post abo
2009/6/18 Ondrej Certik :
>
> On Thu, Jun 18, 2009 at 1:20 PM, William Stein wrote:
>
>> Of related interest, there are 8 publicly visible methods on SageObject:
>>
>> sage: s = SageObject()
>> sage: s.
>> s.category s.db s.dump s.dumps s.rename
>> s.reset_name s.save
On Thu, Jun 18, 2009 at 1:20 PM, William Stein wrote:
> Of related interest, there are 8 publicly visible methods on SageObject:
>
> sage: s = SageObject()
> sage: s.
> s.category s.db s.dump s.dumps s.rename
> s.reset_name s.save s.version
>
> I think I created a
2009/6/18 Nicolas M. Thiery :
>
> On Thu, Jun 18, 2009 at 04:40:50PM +0200, William Stein wrote:
>> On Thu, Jun 18, 2009 at 9:03 AM, Nicolas M.
>> > To ease the reviewing of the category code, and also to make it more
>> > generic and useful, I have extracted the test framework code out of
>> > th
Craig Citro wrote:
> Hi all,
>
> Here's rc3, which *should* be the last rc for this release cycle. I've
> tested it on my laptop and the build farm, and I've had no troubles at
> all, and it's currently going on a few other machines, so hopefully
> that'll turn out fine, too. Please test it and l
On Thu, Jun 18, 2009 at 8:38 PM, Nick Alexander wrote:
>
>
> On 18-Jun-09, at 10:50 AM, Carlo Hamalainen wrote:
>
>>
>> Hi,
>>
>> I'm curious about which debugging environment is most popular among
>> the Sage developers?
>>
>> * print statements only (ugh)
>> * pdb
>> * ddd
>> * Eric4
>> * someth
On 18-Jun-09, at 10:50 AM, Carlo Hamalainen wrote:
>
> Hi,
>
> I'm curious about which debugging environment is most popular among
> the Sage developers?
>
> * print statements only (ugh)
> * pdb
> * ddd
> * Eric4
> * something else?
I use print statements and pdb (both from within emacs). I m
On Fri, Jun 19, 2009 at 3:26 AM, Craig Citro wrote:
>
> I believe that the necessary upgrade bits are sitting here, but I
> haven't tried it:
>
> http://sage.math.washington.edu/home/craigcitro/release/sage-4.0.2.rc3/
Upgraded from sage-4.0.2.rc3 OK on sage.math. But soon after executing
the
Hi,
I'm curious about which debugging environment is most popular among
the Sage developers?
* print statements only (ugh)
* pdb
* ddd
* Eric4
* something else?
I just wrote a short post about how to get Eric4 to work with Sage
since the only instructions I could find (on some mailing list) wer
Hi all,
Here's rc3, which *should* be the last rc for this release cycle. I've
tested it on my laptop and the build farm, and I've had no troubles at
all, and it's currently going on a few other machines, so hopefully
that'll turn out fine, too. Please test it and let me know if you run
into anyt
> No, it would be very nice to have "sage -t foo.sws"... or something.
http://trac.sagemath.org/sage_trac/ticket/6357
Nick
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-d
On Thu, Jun 18, 2009 at 04:49:10PM +0200, William Stein wrote:
> > > Btw: is it possible to run sage -t on a notebook?
>
> No, it would be very nice to have "sage -t foo.sws"... or something.
This is now: http://trac.sagemath.org/sage_trac/ticket/6356
Cheers,
Ni
On Thu, Jun 18, 2009 at 04:40:50PM +0200, William Stein wrote:
> On Thu, Jun 18, 2009 at 9:03 AM, Nicolas M.
> > To ease the reviewing of the category code, and also to make it more
> > generic and useful, I have extracted the test framework code out of
> > the categories and into SageObject.
> >
On Wed, Jun 17, 2009 at 4:49 PM, wrote:
> William Stein wrote:
>>
>> Jason,
>>
>> Unfortunately, I find it highly highly frustrating in tinyMCE that I
>> can't enter a newline (i.e., what shift enter did before you rebound
>> it) without directly editing the html. In my personal copy of Sage,
>>
On Wed, Jun 17, 2009 at 9:02 PM, Nicolas M.
Thiery wrote:
>
> On Wed, Jun 17, 2009 at 06:20:57PM +0100, Martin Albrecht wrote:
>>
>> Hi there,
>>
>> Sage Days 16 is coming up next week in Barcelona. On Tuesday, I will give a
>> talk on how to get started developing Sage. At SD16 many people are at
Nick Alexander wrote:
> * I want to be able to "pop out" or "anchor" an interact and have it
http://www.sagenb.org/home/pub/585/
The code is all client-side, so popping a cell evaluates it. It may be
best to delete all output before reloading.
Strangely, jQuery/UI duplicates the [shift-]cl
On Thu, Jun 18, 2009 at 9:03 AM, Nicolas M.
Thiery wrote:
>
> Hi!
>
> To ease the reviewing of the category code, and also to make it more
> generic and useful, I have extracted the test framework code out of
> the categories and into SageObject.
>
> See also: http://groups.google.com/group
> > I think Bill will not object if this time you do what he did.
>
> :-)
>
> Indeed I would be very happy and appreciative if someone else took
> care of this! I think it would be a good idea to co-ordinate this on
> the sage-devel list. If you feel motivated you could make use of Sage
> trac bu
On Wed, Jun 17, 2009 at 8:11 PM, Jason Grout wrote:
>
> David Joyner wrote:
>> Hi:
>>
>> Sage was mentioned again on slashdot - see the comments to the
>> review of the book Beginning Python Visualization,
>> http://books.slashdot.org/article.pl?sid=09/05/27/1327255
>> BTW, I bought that book and
On Thu, Jun 18, 2009 at 1:35 PM, Marshall Hampton wrote:
>
> I'm having trouble uploading this to anything. On my own laptop,
> after a long time I get "header line too long". I gave up waiting for
> sagenb to load it after about 10 minutes.
You could look at the pdf here instead:
http://wste
4.0.1. built successfully.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/g
I'm having trouble uploading this to anything. On my own laptop,
after a long time I get "header line too long". I gave up waiting for
sagenb to load it after about 10 minutes.
-Marshall
On Jun 17, 10:19 pm, William Stein wrote:
> Hi,
>
> I wrote my MEGA plenary talk, which I'm giving in abou
-- Forwarded message --
From: maxthemouse
Date: Thu, Jun 18, 2009 at 7:26 AM
Subject: Re: fricas and ECL
To: Bill Page
Sorry,
I think I sent you the wrong version. That was the before the reply
from Waldek Hebisch. The following should be correct.
#!/bin/sh
check_error() {
-- Forwarded message --
From: maxthemouse
Date: Thu, Jun 18, 2009 at 7:10 AM
Subject: Re: fricas and ECL
To: Bill Page
On Jun 18, 4:45 am, Bill Page wrote:
> On Wed, Jun 17, 2009 at 9:09 PM, Waldek Hebisch wrote:
> > maxthemouse wrote:
> > ...
> >> What was not clear to me w
Tom Boothby wrote:
> t2 is reporting 4 hours of uptime, though it wasn't responding 3 hours
> ago. Fishy?
I suspect the problem was outside of t2. The machine logged no messages
at all to indicated it had problems, so perhaps a power failure was the
issue.
When the machine came up, the home d
On Thu, Jun 18, 2009 at 12:41 PM, Andrzej Giniewicz wrote:
> Hello,
>
> I've read today your talk "What is on the Horizon" and I really liked
> the idea about making Sage best Statistical software around!!! I
> actually had planned similar project (the design stage, not so good
> with Python still
Support for tearing out docstrings
http://trac.sagemath.org/sage_trac/ticket/6001
is not ready for inspection [1], but it will depend on a few other
tickets. In particular, upgrading jQuery and jQuery UI
http://trac.sagemath.org/sage_trac/ticket/5447
should fix an issue with drag-and-drop.
> Curiously enough, I think you will need very little hand-holding.
> (But I'm willing to answer whatever questions I can.) Hopefully you
> won't have a whole lot of spkgs to update, and merging new code is
> very easy with Craig's apply_ticket.py program. (Check ~ncalexan/bin
> for an hg reposi
2009/6/17 William Stein :
>
> 2009/6/17 eduardo :
>>
>> hi all
>> on o a debian linux, 64 bits i got this failure
>
> This happens if you have the optional cremona database installed. It's
> a known problem (I reported it to trac yesterday).
And very soon afterwards a patch was delivered fixing t
Dear category fans!
The original plan was for Craig to review the most mathematically
oriented (and therefore fun) part of the category patch, namely the
definition of the categories themselves. However he got burned out by
the handling of the Sage releases, and something tells me he coul
hello all,
i'm just giving a try to the binaries found on the website and it
doesn't work:
nemo-henry% /local/apps/sage-3.4.2-i86pc-SunOS+toolchain/sage
--
| Sage Version 3.4.2, Release Date: 2009-05-04 |
|
On 17-Jun-09, at 4:55 PM, Tom Boothby wrote:
> Alright, I'll do a release -- I'm going to need some serious
> hand-holding though.
Curiously enough, I think you will need very little hand-holding.
(But I'm willing to answer whatever questions I can.) Hopefully you
won't have a whole lot o
Hi!
To ease the reviewing of the category code, and also to make it more
generic and useful, I have extracted the test framework code out of
the categories and into SageObject.
See also: http://groups.google.com/group/sage-devel/msg/0586b64f72435629
Anyone up for reviewing it?
Cheers,
56 matches
Mail list logo
