Hi!
I am nearly done with a full Cython-version of cached_method. That's
to say:
1) cdef classes inheriting from Parent or Element can be provided with
cached methods, even if they do not allow attribute assignment.
2) Due to moving cached_method from Python to Cython with cdef'ing
some key metho
On Sunday, April 3, 2011, Keshav Kini wrote:
> On Apr 4, 3:23 am, William Stein wrote:
>> Could we change the default to "git = true" as a patch to the version
>> of hg we distribute with Sage? Or, alternatively, have a patch that
>> prints a warning
>> whenever Sage's hg is used but git = fals
On Apr 4, 3:23 am, William Stein wrote:
> Could we change the default to "git = true" as a patch to the version
> of hg we distribute with Sage? Or, alternatively, have a patch that
> prints a warning
> whenever Sage's hg is used but git = false? The second option would
> be safer, since a use
A friend of mine, Nicole Allen, runs the Student Public Interest
Research Group's "Affordable Textbook Campaign." Her job title is
"Textbook Advocate" - how cool is that?
Part of her job is promoting open source textbooks (how much more
affordable can you get?). She is plotting to have a booth
Was working on some code that required the random shuffling of the order of
a list and noticed that there was both a random() function implemented in
the sage library and a random module in the python standard library.
Importing the latter seems to overwrite the former and I was wondering if
that w
On Sat, Apr 2, 2011 at 5:25 PM, Keshav Kini wrote:
> Indeed. Mercurial's workflow is not really supposed to be carried out
> by sending patches to people (the encouraged behavior is to use `hg
> pull` from other people's repositories), so the default patch / export
> format only includes a subset
the full install log is here:
(I ran make twice, to make sure that wasn't a random hardware
weirdness)
http://boxen.math.washington.edu/home/dima/tmp/sage4.7.aplha3.MacOSX.PPC.install.log.gz
On Apr 4, 12:23 am, Dima Pasechnik wrote:
> -- Forwarded message --
> From: Dima Pasechn
-- Forwarded message --
From: Dima Pasechnik
Date: Apr 3, 10:35 pm
Subject: sage-4.7.alpha3 released
To: sage-release
it doesn't build on MacOSX 10.5.8 PPC, getting stuck at ECL.
Any idea why?
[...]
;*** Lisp core booted
ECL (Embeddable Common Lisp)
;;;
;;; Welcome to b
On 3 April 2011 15:47, Dima Pasechnik wrote:
> IMHO gcc 4.3.0 is not relevant any more, and it's hard to imagine
> anyone needing to build Sage with gcc 4.3.0 now...
But it would still be nice to document whether there are issues with
gcc 4.3.0, since we claim Sage works with gcc >= 4.0.1 and tes
IMHO gcc 4.3.0 is not relevant any more, and it's hard to imagine
anyone needing to build Sage with gcc 4.3.0 now...
On Apr 3, 3:17 pm, "Dr. David Kirkby" wrote:
> The part of the sage manual dealing with installing Sage from source code
>
> http://www.sagemath.org/doc/installation/source.html
>
No I still have to get administrative rights so didn't even had the
canche on working on this.
On Apr 3, 2:26 am, Keshav Kini wrote:
> Yup, this is a great idea. You were working on this during sage days
> 29, right? Any progress?
>
> -Keshav
>
> On Mar 24, 3:14 am, koffie wrote:
>
>
>
> > Since
The part of the sage manual dealing with installing Sage from source code
http://www.sagemath.org/doc/installation/source.html
says "Does not build with gcc 4.3.0 yet, but work is ongoing to fix that"
Is this information true?
I'm updating this section of the manual - see
http://trac.sagemath
12 matches
Mail list logo
