#18107: The codes collection should be a real module
-------------------------------------+-------------------------------------
Reporter: jsrn | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.6
Component: coding theory | Resolution:
Keywords: sd66 | Merged in:
Authors: Johan S. R. | Reviewers: Nathann Cohen
Nielsen | Work issues:
Report Upstream: N/A | Commit:
Branch: | f4604893e1757420d61372d22f33c900ca6a316c
u/jsrn/18107_coding_module | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by jsrn):
Hi Volker,
I fixed the bug you found.
Regarding your other comment, I would recommend that user to import his
`codes` module from a sub-module, like `import mystuff.codes as mycodes`.
Sage injects loads of functions into the global namespace. Injecting
modules as well is a natural next-step, in my opinion, once the global
number of functions is high enough. That requires, as you point out, in
certain circumstances a very slight annoyance on the side of users having
their own modules.
I don't think a good solution is to keep `codes`, and other "collections
of
semi-global functions", as objects, thereby missing out on module
functionality.
--
Ticket URL: <http://trac.sagemath.org/ticket/18107#comment:18>
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.
