#18180: Remove a few unused modules
-------------------------------------+-------------------------------------
Reporter: mmezzarobba | Owner:
Type: enhancement | Status: needs_info
Priority: minor | Milestone: sage-6.6
Component: misc | Resolution:
Keywords: | Merged in:
Authors: Marc Mezzarobba | Reviewers: Nathann Cohen
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/mmezzarobba/18180-cleanup | 2299ec358f67ded1d450453e62de7995bde8acfd
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jhpalmieri):
The safe way is to deprecate first, delete later, precisely because we
don't know what is used "in the wild". I don't see a compelling reason to
do anything else.
I believe that the particular deletions here are probably safe to do now,
but a deprecation now followed by deletion later would be even safer.
> I believe that the custom is to only deprecate things which are somehow
accessible in the global namespace, and that we can remove/change whatever
has to be imported manually.
I don't know this custom. Certainly
`sage.rings.integer_ring_python.iterator(...)` can be run without an
import, just like the deprecated function
`sage.combinat.alternating_sign_matrix.to_monotone_triangle` (for
example).
--
Ticket URL: <http://trac.sagemath.org/ticket/18180#comment:7>
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.
