#17973: Better Sage consistency for naming and calling in linear_code
-------------------------------------+-------------------------------------
Reporter: dlucas | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.6
Component: coding theory | Resolution:
Keywords: | Merged in:
Authors: David Lucas | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dlucas/better_sage_consistency_for_naming_and_calling_in_linear_code|
7b7395eae5ca1897fa9edf445c5317b1ada00584
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by ncohen):
* status: needs_review => needs_work
Comment:
Hello !
I would say that this is good to go, except for one detail: could you
deprecate the methods using `deprecated_function_alias` instead of doing
it manually? There are some advantages, like a warning in the doc of the
deprecated function. Besides, they do not appear in the lists of
undocumented functions.
http://www.sagemath.org/doc/developer/coding_in_python.html#deprecation
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/17973#comment:4>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
