On Dec 16, 6:32 pm, Simon King <simon.k...@uni-jena.de> wrote:
> Hi all!
>
> On 15 Dez., 15:39, Simon King <simon.k...@uni-jena.de> wrote:
>
> > This is why I suggest the scenario "the ring constructor prints a
> > warning if the variable name is not a string": QQ[x] or
> > PolynomialRing(QQ,[singular],1) would result in a warning, but the
> > *intended* use QQ['x'] or R.<singular>=QQ[] would be OK.
>
> I suggest the deprecation at #10483, ready for review.
>
> Cheers,
> Simon
Hi Simon,
What does it mean 'deprecation'? Will this mean that at some point
sage: var('x')
sage: QQ[x]
will be invalid code?
I am against that change.
sage: K.<x,y> = QQ[]
Is not valid python, it needs the preparser and will not work on a .py
file
sage: QQ['x']
Is just unconfortable when you are creating several rings with
variables with the same names.
If this feature of current sage for creating QQ[x] makes people less
like to try sage, we should find polite ways to tell what is the
expected behavior or use, maybe a warning is ok, but I do not think
that eliminating options in the language is a good option.
Bests,
Luis
--
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
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
