#18024: Mutability of tableaux part II: replacing CombinatorialObject by
ClonableList
-------------------------------------+-------------------------------------
Reporter: darij | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.6
Component: combinatorics | Resolution:
Keywords: tableaux, sage- | Merged in:
combinat, mutability, | Reviewers: Josh Swanson
ClonableList, days64 | Work issues:
Authors: Jan Keitel, Darij | Commit:
Grinberg | c1c6a729de7fdbc8f77846afedfd5cf6c9f28005
Report Upstream: N/A | Stopgaps:
Branch: |
public/TransitionClonable |
Dependencies: #15862 |
-------------------------------------+-------------------------------------
Changes (by jpswanson):
* reviewer: => Josh Swanson
* work_issues: fix __setstate__'s such that the doctests work =>
Comment:
Made a few minor reviewer changes, so as soon as someone signs off on
those we can call this good.
After looking into the old pickles issue, I decided to just remove them
for the following reasons.
1. We had already removed a couple of old pickle tests and none of the
contributors on this ticket had yet complained.
2. Frankly, I haven't found anyone who seems to really care about old
pickles breaking, except for some old posts by William Stein. The most
relevant sage-devel thread I found was
[https://groups.google.com/forum/#!searchin/sage-devel/pickles/sage-devel
/KjnxIXO-xnE/YvTX9PV7LAsJ this one], where an old k-Schur class had been
deprecated though it had some old pickles in the pickle jar, and efforts
to override proved unsuccessful. Discussion eventually died off and the
old pickles were just removed. In a similar vein, discussion about
refreshing the pickle jar in #11720 never went anywhere, and there are
several other examples of pickle-related discussion that seem to trail off
into nothingness. I also asked Andrew Ohana, who doesn't care about them,
and I personally do not care about them. To be fair, I may have missed
people or oversimplified their views.
3. The consensus I've been able to gather is that pickling is a terrible
archival format, one should not use it alone to store important
information for many years, and if the worst happens, you should be able
to get an old version of sage to recover your data. I also haven't found
evidence of many users complaining about old pickles breaking.
4. The k-Schur sage-devel thread I linked above makes it seem that a large
amount of time and effort was wasted on that particular issue. Even if
maintaining backwards compatibility of old pickles is a worthwhile goal,
I'm not at all convinced it's worth stealing development time.
If others care about these pickle issues, please let me know!
----
New commits:
||[http://git.sagemath.org/sage.git/commit/?id=c1c6a729de7fdbc8f77846afedfd5cf6c9f28005
c1c6a72]||{{{minor change, and fixing a broken iterator}}}||
--
Ticket URL: <http://trac.sagemath.org/ticket/18024#comment:23>
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.
