#14748: Deal with DeprecationWarning(s) that appear when using the BoundClass
----------------------------------+-----------------------------------------
Reporter: strogdon | Owner: jason
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.11
Component: misc | Resolution:
Keywords: | Work issues: add regression doctest
Report Upstream: N/A | Reviewers: Travis Scrimshaw
Authors: Steven Trogdon | Merged in:
Dependencies: | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by strogdon):
Sorry for the delay. I've had limited internet access for the last several
days and things will not improve for the next 4 or 5 days. Initially I
thought the doctest would be straightforward? However, It's not as easy to
catch deprecations with the doctest framework as it is to catch them from
the Sage prompt. It may be that bindable_class.py will have to be modified
to import the warnings module before a meaningful doctest can be
implemented. Thus, I'm not exactly sure what's the best way to proceed. Of
course, one could implement a doctest with calls to
{{{QuasiSymmetricFunctions}}} that exhibited the initial
{{{DeprecationWarning}}} at trac #14136, but I don't see that as failsafe.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14748#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.
