#13723: Moving hamming_weight from sage.coding to sage.modules
-------------------------------------------------+--------------------------
Reporter: tfeulner | Owner: wdj
Type: enhancement | Status: new
Priority: minor | Milestone: sage-5.6
Component: coding theory | Resolution:
Keywords: Hamming weight, coding theory | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------------------------+--------------------------
Comment (by tfeulner):
In my opinion, we should deprecate the function hamming_weight() in
sage/coding/. Why should we have a global function in an object oriented
language as Python is? In my experience as a new developer, this is one of
the main problems of Sage that you have several functions doing the
same... The same is true for some user who shouldn`t be forced to have a
look into the source code to decide which function he/she should use.
Finally, the docstring tells us that ``v`` has to be a vector, so the old
code will only work in those cases which are catched by the new patch so I
guess that we will only catch an `AttributeError` which we will produce in
the following 'old code`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13723#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
