#20667: Do not use resetwarnings
-------------------------------------+-------------------------------------
Reporter: novoselt | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-7.3
Component: user interface | Resolution:
Keywords: | Merged in:
Authors: Andrey | Reviewers:
Novoseltsev | Work issues:
Report Upstream: N/A | Commit:
Branch: | ed746286af38545c69edfc77c3a9f1cfde4665fd
u/novoselt/dont_reset_warnings | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Changes (by novoselt):
* cc: jsrn, jdemeyer, vbraun (added)
* commit: => ed746286af38545c69edfc77c3a9f1cfde4665fd
* status: new => needs_review
Comment:
Some warnings that had to be dealt with have surfaces: I fixed all but 2
of them, for which I have added deprecation warnings in doctests:
- weave is now a separate package and should not be used from scipy
- `ShardPosetElement` derives from `tuple`, which is against Sage
guidelines
There is some code for matrices that has to be removed together with
custom deprecation, I've openened #20665.
----
New commits:
||[http://git.sagemath.org/sage.git/commit/?id=ed746286af38545c69edfc77c3a9f1cfde4665fd
ed74628]||{{{Do not use resetwarnings(), rather setup filters
appropriately.}}}||
--
Ticket URL: <http://trac.sagemath.org/ticket/20667#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 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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
