On 12/8/10 10:47 PM, Dima Pasechnik wrote:
On Dec 9, 3:36 am, mhampton wrote:
+1. I think it usually makes sense to stick with numpy conventions
(which are in turn mostly designed to follow matlab).
Matlab... Oy gevalt. Will you suggest renaming binomial() as
nchoosek() ? :-)
I could se
please report Sage version, OS version, compiler version...
On Dec 9, 2:48 am, Sancho wrote:
> I run: sage -i wxPython-2.8.7.1
>
> I get the following error.
>
> /cs/public/lib/pkg/sage/sage-local/spkg/build/wxPython-2.8.7.1/
> wxPython-src-2.8.7.1/bld/bk-deps g++ -c -o monodll_gsockgtk.o -I.pch/
On Dec 7, 6:56 pm, Robert Miller wrote:
> I'm not sure it is a good idea to *remove* the methods from the object
> of which they are a natural function. I've seen this argument many
> times before, and I really like this as an organizing method.
> Everything else you say seems like a good idea t
On Dec 9, 3:36 am, mhampton wrote:
> +1. I think it usually makes sense to stick with numpy conventions
> (which are in turn mostly designed to follow matlab).
Matlab... Oy gevalt. Will you suggest renaming binomial() as
nchoosek() ? :-)
Dima
>
> -Marshall
>
> On Dec 3, 10:38 pm, Jason Grout
> > in Mathematica (and maybe something like it in Sage).
> > Expand[(x^(2^(2^29))+1)^2]
Sage uses Ginac/Pynac for this. It just hangs:
sage: expand((x^(2^(2^29))+1)^2)
^C
Unhandled SIGSEGV: A segmentation fault occurred in Sage.
Th
I run: sage -i wxPython-2.8.7.1
I get the following error.
/cs/public/lib/pkg/sage/sage-local/spkg/build/wxPython-2.8.7.1/
wxPython-src-2.8.7.1/bld/bk-deps g++ -c -o monodll_gsockgtk.o -I.pch/
wxprec_monodll -D__WXGTK__ -I../src/tiff -I../src/jpeg -I../src/
png -I../src/zlib -I../src/regex
On 8 December 2010 23:31, rjf wrote:
>
>
> On Dec 8, 10:45 am, kcrisman wrote:
>> > And why should anyone care? Do you think that Wolfram Alpha will last
>> > longer than Mathematica?
That's such a stupid question, I'm not going to answer it.
>> I think the point was that not everyone who migh
On Dec 8, 10:45 am, kcrisman wrote:
> > And why should anyone care? Do you think that Wolfram Alpha will last
> > longer than Mathematica?
>
> I think the point was that not everyone who might want to do this
> would have access to Mma, but that (for now) they would all have
> access to W|A. J
On Wed, Dec 8, 2010 at 2:41 PM, Christian Stump
wrote:
> Salut,
>
> here is the code in the notebook:
>
> class Goo():
> def interact(self):
> @interact
> def _(n=selector([0,1,2],nrows=1,default=0, label="label")):
> return
> interactive=interact
>
> if you run
>
> Goo()
Salut,
here is the code in the notebook:
class Goo():
def interact(self):
@interact
def _(n=selector([0,1,2],nrows=1,default=0, label="label")):
return
interactive=interact
if you run
Goo().interact()
in a new cell, and
Goo().interactive()
in another, you see t
+1. I think it usually makes sense to stick with numpy conventions
(which are in turn mostly designed to follow matlab).
-Marshall
On Dec 3, 10:38 pm, Jason Grout wrote:
> In numpy, the conjugate transpose is A.H, the transpose is A.T, and the
> inverse is A.I. I'd love if we adopted those sho
> And why should anyone care? Do you think that Wolfram Alpha will last
> longer than Mathematica?
I think the point was that not everyone who might want to do this
would have access to Mma, but that (for now) they would all have
access to W|A. Just to clarify - I don't really have a horse in t
On Dec 6, 11:15 am, Robert Bradshaw
wrote:
> I agree, people of all backgrounds can make significant contributions.
Logically, nothing to argue with
"There may be a person X of {no particular specified background} who
can make a significant contribution"
I think we agree that we have higher
On Dec 6, 8:01 am, David Kirkby wrote:
> This presupposes that people of fairly high mathematical knowledge are
> good at writing software.
>
> I'm yet to be convinced that having a PhD in maths, or studying for
> one, makes you good at writing software tests
I quite agree. Or even writing so
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
The keyword is "multiedges" not "multi_edges". Weird artifact of using
NetworkX as the default implementation historically...
On 7 December 2010 20:57, mhs wrote:
> Hi,
>
> I encountered a strange behaviour of the add_edges method for DiGraphs
> (using SAGE 4.5.1). Perhaps this is intended behavi
Interesting discussion, I never realized that we are using two interpretations for this same word
depending on the context!
My 2 cents:
In my favorite linear algebra book:
F. R. Gantmacher, The theory of matrices. (1959)
The adjoint of a matrix is defined 2 times with the two meanings!!! (at le
On Dec 8, 5:35 am, Simon King wrote:
> How case and noise resistant is the buildbot?
...
> And what about an indentation?
...
As far as I can tell, casing and spacing should both be irrelevant --
the functions "extract_patches" and "extract_depends_on" (from trac.py
in the buildbot source) bot
Having just updated ECL and Maxima, there's a note on the ECL list
there should be a new stable version before the end of the month.
By reading this, it appears VirtualBox is working much better now,
allowing improved testing.
Dave
-- Forwarded message --
From: Juan Jose Garcia-R
On Tue, 07 Dec 2010 at 11:55PM -0800, Robert Bradshaw wrote:
> The patchbot works by creating branches so that it doesn't have to
> create a entirely new copy of Sage for every ticket. Of course scripts
> doesn't play nicely with branching, so it can't even handle this.
> Eventually it should be ex
PS:
On 8 Dez., 11:22, Robert Bradshaw
wrote:
> Just have a line that says "depends on #8807 #10318"
How case and noise resistant is the buildbot?
E.g., above, you advised `put a line in any comment that says "Apply
foo.diff"` - upper case. Here you advise "depends" - lower case.
By "a line in
Hi Robert,
On 8 Dez., 11:22, Robert Bradshaw
wrote:
> Just have a line that says "depends on #8807 #10318"
Thank you!
Cheers,
Simon
--
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
On Wed, Dec 8, 2010 at 2:06 AM, Simon King wrote:
> Hi!
>
> Admittedly I did not follow the development of the buildbot.
>
> Am I right that it takes trac ticket, applies the patches and then
> tests? That would indeed be awesome.
>
> But how can one explain dependencies to the build bot. Concrete
Hi!
Admittedly I did not follow the development of the buildbot.
Am I right that it takes trac ticket, applies the patches and then
tests? That would indeed be awesome.
But how can one explain dependencies to the build bot. Concrete
example: How can I achieve that the buildbot first applies the
On 2010-12-08 06:18, Dan Drake wrote:
> propose "patchbot". Thoughts?
>
> Second, I have two patches on a ticket
> (http://trac.sagemath.org/sage_trac/ticket/10440); one gets applied to
> the Sage library, the other to the scripts repo. How do I tell
> what-we-currently-call-buildbot where to appl
On Wed, Dec 8, 2010 at 12:54 AM, Johan S. R. Nielsen
wrote:
> Wow, this is really cool! Great work! Also, great plans for ways to
> let people run their own buildbots, hooked up to the central server.
> With customisation so ones own patches will be prioritised whenever
> needed, hopefully a lot o
Wow, this is really cool! Great work! Also, great plans for ways to
let people run their own buildbots, hooked up to the central server.
With customisation so ones own patches will be prioritised whenever
needed, hopefully a lot of people will feel that it's really _easier_
for them to have a build
27 matches
Mail list logo
