The following code produces the weird result:
sage: R.=QQ[]
sage: S.=R[]
sage: u=FractionField(S)(x^2+y^2)
sage: v = u.numerator()/u.denominator()
sage: print u.numerator().parent()
sage: print v.numerator().parent()
Output:
Multivariate Polynomial Ring in x, y over Univariate Polynomial Ring
On Thu, Jun 13, 2019 at 8:28 PM Dima Pasechnik wrote:
>
>
>
> On Thu, Jun 13, 2019 at 7:21 PM Brandon Gontmacher
> wrote:
>>
>> Hi,
>>
>> I did allocate more memory and this cleared up the issue! Thanks for that.
>> I'm now in a situation where as expected the build is taking a lot of time
>>
On Friday, June 14, 2019 at 8:16:58 PM UTC+9, Dima Pasechnik wrote:
>
> On Fri, Jun 14, 2019 at 12:04 PM Kwankyu Lee > wrote:
> >
> > Hi
> >
> > I noticed that the coercion section of the sage reference manual
> mentions _r_action_ and _l_action methods instead of _act_on_ and
>
On Fri, Jun 14, 2019 at 12:04 PM Kwankyu Lee wrote:
>
> Hi
>
> I noticed that the coercion section of the sage reference manual mentions
> _r_action_ and _l_action methods instead of _act_on_ and _acted_upon_
> methods, while it seems that the former methods were replaced with the latter
>
Hi
I noticed that the coercion section of the sage reference manual mentions
_r_action_ and _l_action methods instead of _act_on_ and _acted_upon_
methods, while it seems that the former methods were replaced with the
latter methods 10 years ago in #5597!
Am I right? Then this is quite
