[sage-devel] setuptools install problem

This comes up frequently when running patchbot in SMC. Recently, in one run two tickets built fine on top of 6.2.rc2, then suddenly three other failed due to this. The tickets are unrelated, and at least one is known to pass in another run, and it also builds fine on another system. It also happen

Re: [sage-devel] Re: Problem compiling sage 6.2.rc0-develop with macosx/mavericks

I now have a working version sage! I should qualify this: I have a working version of 6.2.rc0 but I am still unable to compile 6.1.1. I think that this is because of #15937 . This patch is included in 6.2.rc0 and it fixes issues between singular and the ve

[sage-devel] Re: Regarding Braid project and its integration in Sage

Hi Marco, On 2014-05-04, mmarco wrote: > That sounds a lot like rewriting it. Why? > El domingo, 4 de mayo de 2014 17:21:21 UTC+2, Volker Braun escribi=C3=B3: >> >> I've actually looked at the code. If we really want to use it we'd really= >> need to turn it into a shared library, strip out deb

[sage-devel] Re: Regarding Braid project and its integration in Sage

That sounds a lot like rewriting it. El domingo, 4 de mayo de 2014 17:21:21 UTC+2, Volker Braun escribió: > > I've actually looked at the code. If we really want to use it we'd really > need to turn it into a shared library, strip out debugging code, and > probably replace the custom bigint libr

Re: [sage-devel] near-field

On Sat, May 03, 2014 at 03:22:59PM +0200, Vincent Delecroix wrote: > I would like more projective planes seen as incidence structure. In > order to do so I need to introduce what are called near-field [1]. > Which is not exactly a division ring: the distributivity fail on one > of the side. > > Do

[sage-devel] Re: Regarding Braid project and its integration in Sage

I've actually looked at the code. If we really want to use it we'd really need to turn it into a shared library, strip out debugging code, and probably replace the custom bigint library with gmp/mpir. On Saturday, May 3, 2014 10:29:23 PM UTC+2, Amit Jamadagni wrote: > > Hello all, >

[sage-devel] Re: Regarding Braid project and its integration in Sage

> > Hoping to hear from the community.Thanks. > Personally, I would start by stress-testing the code on a variety of inputs to determine it's robustness. If it crashes a lot, there's not much point wrapping it. On the other hand, if it turns out to be bullet-proof, I would recommend against

Re: [sage-devel] Finishing high-school math book, 3 short questions about future of Notebook vs SMC

On Sun, May 4, 2014 at 5:55 AM, Andrzej Giniewicz wrote: > Hello, > > I haven't been following all developments of notebook, because I've > spent quite some time (almost 2 years) co-authoring a book covering > high-school level math using Sage (matching all topics covered in > schools in Poland, p

[sage-devel] Finishing high-school math book, 3 short questions about future of Notebook vs SMC

Hello, I haven't been following all developments of notebook, because I've spent quite some time (almost 2 years) co-authoring a book covering high-school level math using Sage (matching all topics covered in schools in Poland, promoting both math and computers as means to understand material most

[sage-devel] Re: Hoping to develop Game Theoretical capabilities in to Sage

Thanks Kris, On 2 May 2014 19:12, kcrisman wrote: > We've already corresponded about this privately, but I wanted to publicly > support this proposal and offer help with it, given that it is a lot closer > to my current research than anything else in Sage ;-) In particular, I > think it is very

[sage-devel] Re: git diff branch1..develop

I'll do the password reset On Sunday, May 4, 2014 9:57:20 AM UTC+2, Ralf Stephan wrote: > > On Friday, May 2, 2014 12:07:35 AM UTC+2, Volker Braun wrote: >> >> Trac password or ssh password for the git authentication? You shouldn't >> need a trac password (though I probably don't test that), but

[sage-devel] Re: git diff branch1..develop

On Friday, May 2, 2014 12:07:35 AM UTC+2, Volker Braun wrote: > > Trac password or ssh password for the git authentication? You shouldn't > need a trac password (though I probably don't test that), but you need a > ssh key unless you follow the "Readonly repository" instructions. > I just instal