#5294: Pickle Jar documentation
--------------------------------------------+-------------------------------
       Reporter:  hivert                    |         Owner:  tba     
           Type:  defect                    |        Status:  new     
       Priority:  major                     |     Milestone:  sage-5.5
      Component:  documentation             |    Resolution:          
       Keywords:  picklejar, documentation  |   Work issues:          
Report Upstream:  N/A                       |     Reviewers:          
        Authors:  Andrew Mathas             |     Merged in:          
   Dependencies:                            |      Stopgaps:          
--------------------------------------------+-------------------------------

Comment (by andrew.mathas):

 Replying to [comment:3 roed]:
 > The SIGABRT is certainly a bug, and a quick google search doesn't reveal
 any tickets related to it.  Opening a new ticket seems reasonable.  What's
 the doctest that fails?

 It's essentially this: it is a doc test below from unpickle_all which ends
 with a call to en_unpickle_all(). As all doctests are timed I assume the
 the doctest is running inside of (something like) timeit().

 {{{
 sage: from sage.structure.sage_object import unpickle_all,
 register_unpickle_override
 sage: class A(CombinatorialObject,sage.structure.element.Element):
 ...       pass # to break a pickle
 sage:
 register_unpickle_override('sage.combinat.tableau','Tableau_class',A) #
 breaking the pickle
 sage: unpickle_all()  # long time
 }}}

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5294#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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to