[sage-devel] Re: coercion issue

2015-02-05 Thread Vincent Delecroix
Sorry, I press enter to fast. There is a coercion problem. The result of division of GF(5)['x'] by ZZ should live in GF(5)['x']. But right now the coercion model thinks that it should go to the fraction field... (see the example in my first mail). Is there a ticket related to that issue? Does anyb

[sage-devel] Re: coercion issue?

2009-05-31 Thread Bill Hart
Thanks for looking into that David and Martin. It certainly saved a whole load of headache for me!! Bill. On 31 May, 06:46, David Harvey wrote: > This is nowhttp://sagetrac.org/sage_trac/ticket/6168. > > david > > On May 30, 12:03 pm, Bill Hart wrote: > > > Regarding compilation with debug, zn

[sage-devel] Re: coercion issue?

2009-05-31 Thread Martin Albrecht
On Sunday 31 May 2009, David Harvey wrote: > This is now http://sagetrac.org/sage_trac/ticket/6168. > > david I fixed the issue in a patch attached to #6168. Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E

[sage-devel] Re: coercion issue?

2009-05-30 Thread David Harvey
This is now http://sagetrac.org/sage_trac/ticket/6168. david On May 30, 12:03 pm, Bill Hart wrote: > Regarding compilation with debug, zn_poly is passed the flag -DNEBUG > for a couple of files, instead of -DNDEBUG. This is a sloppy typo on > my part. Originally I think I took the output from t

[sage-devel] Re: coercion issue?

2009-05-30 Thread Bill Hart
Regarding compilation with debug, zn_poly is passed the flag -DNEBUG for a couple of files, instead of -DNDEBUG. This is a sloppy typo on my part. Originally I think I took the output from the zn_poly configure script, but in the latest version there were some new files, and I guess I added the ta

[sage-devel] Re: coercion issue?

2009-05-29 Thread David Harvey
On May 29, 10:54 pm, David Harvey wrote: > Hmmm let me try again. Would appreciate help from people familiar with > FLINT wrapper and/or coercion system. > > sage: R. = PolynomialRing(Integers(121)) > sage: S. = PolynomialRing(Integers(11)) > sage: S(50*x) > 6*y > sage: R(S(50*x)) > 50*x     # !

[sage-devel] Re: coercion issue?

2009-05-29 Thread David Harvey
Hmmm let me try again. Would appreciate help from people familiar with FLINT wrapper and/or coercion system. sage: R. = PolynomialRing(Integers(121)) sage: S. = PolynomialRing(Integers(11)) sage: S(50*x) 6*y sage: R(S(50*x)) 50*x # !! I think what's actually happening is that the underly

[sage-devel] Re: coercion issue?

2009-05-29 Thread David Harvey
I'm an idiot, it's a not a bug. I misunderstood the definition of change_ring. Sorry for the noise. david On May 29, 7:46 pm, dmharvey wrote: > Is this a bug? > > sage: version() > 'Sage Version 3.4.2, Release Date: 2009-05-05' > sage: S. = PolynomialRing(Integers(14641)) > sage: f = 1 + 9581*t

[sage-devel] Re: Coercion issue between sparse and dense polynomial rings

2008-06-27 Thread Robert Bradshaw
On Jun 26, 2008, at 10:56 PM, Carl Witty wrote: > Consider the following Sage run, from Sage 3.0.3: > > sage: x1 = PolynomialRing(ZZ, 'x').gen() > sage: x2 = PolynomialRing(ZZ, 'x', sparse=True).gen() > sage: (x1+x2).parent() > Univariate Polynomial Ring in x over Integer Ring > sage: (x2+x1).par