#15445: A codes.<tab> object for Sage's codes
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-5.13
enhancement | Resolution:
Priority: major | Merged in:
Component: | Reviewers:
coding theory | Work issues:
Keywords: | Commit:
Authors: | a583c02be72a4ac9e5c998615218efc83deb3c3d
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
u/ncohen/15445 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by ppurka):
Replying to [comment:4 ncohen]:
> They will tell me to put deprecation warnings everywhere for one year
`T_T`
Ah yes! That solves it! Put deprecation everywhere. `:D` On a more serious
note, it might be confusing if the codes are available both as, say,
`HammingCode` and `codes.HammingCode`. So, it is better that something is
done about it and a clean interface is provided.
I am actually quite happy to see a `codes.<tab>`. That keeps it clean and
it is easy to remember. Instead of trying to remember all the individual
codes, I only need to remember `codes` and then a tab will show me all the
codes that are available in Sage.
--
Ticket URL: <http://trac.sagemath.org/ticket/15445#comment:5>
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/groups/opt_out.
