#16275: Hom: introduce a check argument to simplify the unpickling detection
logic
-------------------------------------+-------------------------------------
Reporter: nthiery | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.2
Component: categories | Resolution:
Keywords: homset, pickling | Merged in:
Authors: Nicolas M. Thiéry | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nthiery/hom__introduce_a_check_argument_to_simplify_the_unpickling_detection_logic|
ae3ca8080a8412891722695d1e24e1dfe374d787
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:18 SimonKing]:
> Replying to [comment:16 nthiery]:
> > One thing: `domain not in category` will possibly call
> > `domain.category()` with the caveats that were mentioned on #14793.
>
> Indeed, that's part of the problem with the broken pickle
:attachment:broken_pickle.sobj
No, it isn't. The caveat was that calling `domain.category()` stores the
returned category, and it may then be the case that
`domain._is_category_initialized()` returns True, even though the category
was too large.
In any case, when we only raise an error if the category does not match
'''and''' `O._is_category_initialized()` is true, then the previously
broken pickle can be unpickled.
So, question: How can I post the updated picklejar?
--
Ticket URL: <http://trac.sagemath.org/ticket/16275#comment:19>
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.
