#19244: Broken doctest in src/sage/categories/fields.py
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: needs_work
Priority: blocker | Milestone: sage-6.9
Component: memleak | Resolution:
Keywords: random_fail | Merged in:
Authors: Simon King | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/SimonKing/broken_doctest_in_src_sage_categories_fields_py|
0d97c7db960aa058b7cb1c60aea839dbc3d161e9
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by jdemeyer):
* status: needs_review => needs_work
Comment:
Replying to [comment:3 SimonKing]:
> This could be done by storing the output of gc.get_object() in a
variable. It creates strong references to all previously created
uncollected objects and will thus make the test stable.
>
> What solution do you prefer? I prefer the second solution, since I am
not sure whether the theory behind my previous solution is correct.
I agree.
--
Ticket URL: <http://trac.sagemath.org/ticket/19244#comment:4>
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.
