#17569: Allow creating finite fields without a variable name
-------------------------------------+-------------------------------------
Reporter: pbruin | Owner:
Type: enhancement | Status: needs_review
Priority: minor | Milestone: sage-7.1
Component: finite rings | Resolution:
Keywords: | Merged in:
Authors: David Roe | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/roed/allow_creating_finite_fields_without_a_variable_name|
2fcbc08667d7048d1f9a2691c8e4e9a2eff66001
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by dimpase):
Replying to [comment:9 roed]:
> Currently, you can feed random keyword arguments to most (all?) of the
finite field constructors and they'll have no effect.
> {{{
> sage: GF(27,'a',blah=True)
> Finite Field in a of size 3^3
> }}}
> I don't see a problem in having `conway` behave in the same manner. Why
raise a deprecation warning when the code can just keep working without
any change?
You are effecting a change in the behaviour of the code. E.g.
`sage: GF(27,'a',conway=True)` currently throws an exception, and this is
will no longer be the case. (Perhaps one can come up with a more
interesting example, but that's beside the point).
--
Ticket URL: <http://trac.sagemath.org/ticket/17569#comment:10>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
