Re: [sage-devel] Re: Motivation for ElementMethods in categories

On Thu, Sep 19, 2013 at 9:48 AM, Peter Bruin wrote: > I don't think I said that I wanted more static inheritance. > > >> Basically, you want >> >> class IntegralDomainElement(Element): >> ... >> >> class IntegralDomain(Parent): >> ... >> >> class EuclideanDomainElement(

[sage-devel] Re: Answers to queries about flooved.com, and some questions as well...

Thanks Jason, and sorry for being so late to reply. We are definitely intending to enable the users to link to their annotations and share them outside of the platform, even though I imagine people will need the text itself a lot of the time in order to fully understand what they are saying. I

Re: [sage-devel] Re: Answers to queries about flooved.com, and some questions as well...

Quite the contrary, we are looking at the specs when designing our annotations features. We hope that when it is fully developed it'll be 'up to spec'. :) On Wednesday, 4 September 2013 10:29:00 UTC+1, Volker Braun wrote: > > In particular, hypothes.is works on a and implements the open annotati

Re: [sage-devel] Re: Answers to queries about flooved.com, and some questions as well...

Thanks - see my reply to Jason above Uri On Wednesday, 4 September 2013 09:11:12 UTC+1, Burcin Erocal wrote: > > On Tue, 03 Sep 2013 11:31:43 -0500 > Jason Grout > wrote: > > > On 9/3/13 11:26 AM, Jason Grout wrote: > > > And a collaborative annotation system for books is certainly > > > somet

Re: [sage-devel] Re: Motivation for ElementMethods in categories

> So the proposed change isn't really that big after all, just a > renaming and the addition of one level of nesting. > > class MyCategory(Cagetory_singleton): > class Object: > ... > class Element: > ... > >I'm against this because that means there is a

[sage-devel] Re: Towards git development

I guess I found the documentation I had been expecting: http://trac.sagemath.org/wiki/QuickStartSageGit Makes me realize that “master” isn't the same as “public/sage-git/master”, so it seems I was using the wrong branch. I'm doing things by the book now, and everything looks good so far. I also

[sage-devel] Re: Are Laurent polynomials really this broken? (or is it me?)

On Thursday, September 19, 2013 10:10:26 AM UTC-7, Travis Scrimshaw wrote: > > Let me also make explicit the question: Given ZZ[t, t^-1], do we want 1 / > (2*t) to be in the fraction field or in QQ[t, t^-1]? > > I'm leaning towards the latter since it is a "smaller/more simple" ring > (and I real

[sage-devel] Re: Are Laurent polynomials really this broken? (or is it me?)

Hey everyone, At least some of this for univariate Laurent rings is fixed in #11726 (although this currently depends on #14261, which is where this problem comes from): sage: R. = LaurentPolynomialRing(ZZ) sage: 1 / t t^-1 Let me also make explicit the question: Given ZZ[t, t^-1], do we w

[sage-devel] Re: Are Laurent polynomials really this broken? (or is it me?)

On Thursday, September 19, 2013 1:34:02 AM UTC-7, Andrew Mathas wrote: > Everything is correct except, I think, the last line: x^-1 it NOT defined > so this should be returning an error rather than coercing into the field of > fractions. > If you're mainly interested in laurent polynomials

Re: [sage-devel] Re: Motivation for ElementMethods in categories

On Thu, Sep 19, 2013 at 10:30 AM, Peter Bruin wrote: > Hi Robert, > > >> > I would expect the category framework to figure out that if R is an >> > object >> > in EuclideanDomains, then R.element_class should dynamically inherit >> > from >> > both EuclideanDomainElement and IntegralDomainElement.

Re: [sage-devel] Re: Motivation for ElementMethods in categories

I don't think I said that I wanted more static inheritance. Basically, you want > > class IntegralDomainElement(Element): > ... > > class IntegralDomain(Parent): > ... > > class EuclideanDomainElement(IntegralDomainElement): > def xgcd(self, other): >

Re: [sage-devel] Re: Motivation for ElementMethods in categories

Hi Robert, > I would expect the category framework to figure out that if R is an > object > > in EuclideanDomains, then R.element_class should dynamically inherit > from > > both EuclideanDomainElement and IntegralDomainElement. > > It already does. R need not descend from EuclideanDomain, it

[sage-devel] Re: Towards git development

Note the big red warning on the top of the page. Use public/sage-git/master instead of master until things settle down. git fetch trac u/user/description git checkout -b trac_master FETCH_HEAD make On Thursday, September 19, 2013 1:20:14 PM UTC+1, martin@gmx.net wrote: > > I'm still trying

[sage-devel] Re: Towards git development

Sorry, should have been git fetch trac public/sage-git/master git checkout -b trac_master FETCH_HEAD make -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-dev

Re: [sage-devel] Re: Deprecation of %load

On Sep 19, 2013 6:32 AM, "Jason Grout" wrote: > > On 9/19/13 8:30 AM, John Cremona wrote: >> >> If you have Magma, what I am thinking about is there called iload and >> used like load. > > > Ah. In Sage, we do have %iload already implemented. IPython doesn't have something like this, if I recall

[sage-devel] Re: Deprecation of %load

On 9/19/13 8:30 AM, John Cremona wrote: If you have Magma, what I am thinking about is there called iload and used like load. Ah. In Sage, we do have %iload already implemented. IPython doesn't have something like this, if I recall correctly. Thanks, Jason -- You received this message b

Re: [sage-devel] Re: Deprecation of %load

On 19 September 2013 14:21, Jason Grout wrote: > On 9/19/13 8:11 AM, John Cremona wrote: >> >> In IPython's %load does the whole file contents really go into the one >> next prompt? Or do you get the file one line at a time? That would >> be a useful option for demos. > > > In IPython, you get t

[sage-devel] Re: Deprecation of %load

On 9/19/13 8:11 AM, John Cremona wrote: In IPython's %load does the whole file contents really go into the one next prompt? Or do you get the file one line at a time? That would be a useful option for demos. In IPython, you get the whole file contents, but it will ask you if the file is over

[sage-devel] Re: Deprecation of %load

%runfile is a misnomer if you can also use it on urls. %run is shorter and better named. So I would be in favor of the third option. [X] Add Sage-specific features to %run -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Deprecation of %load

In IPython's %load does the whole file contents really go into the one next prompt? Or do you get the file one line at a time? That would be a useful option for demos. I have been continuing to use %load and ignoring the deprecation warning. Your first option seems simplest, but I do not have s

[sage-devel] Deprecation of %load

In the move to IPython 0.13 that happened in Sage 5.7, I deprecated %load and renamed the command %runfile. This was because IPython introduced a %load command with very different semantics. In IPython, %load makes the next prompt (or input box in the notebook) contain the code of the file, w

[sage-devel] Towards git development

I'm still trying to come to grips with the transition to git. I hear about it in this threadand now wanted to use it for a requested rebase . Here is what I did: 1. Checked out

[sage-devel] Re: Are Laurent polynomials really this broken? (or is it me?)

Hi Andrew, On 2013-09-19, Andrew Mathas wrote: > Thanks for the clarification Nils. So Laurent polynomials are not playing > well with their coefficients, but I wonder if the real issue is that even > polynomials over rings have not been implemented carefully eough. Consider: > > sage: A.=Polyn

[sage-devel] Re: Are Laurent polynomials really this broken? (or is it me?)

On Thursday, 19 September 2013 08:51:02 UTC+2, Nils Bruin wrote: > > > I think the error is elsewhere: > > sage: P.=LaurentPolynomialRing(ZZ,2) > sage: p=2*u**-1*v**-1+u*v > sage: [ type(c) for (exp,c) in p.dict().iteritems()] > [sage.rings.rational.Rational, sage.rings.rational.Rational] > > The