New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple loops and edges are lost upon pickling #10916
Comments
comment:3
Attachment: trac_10916_pickling_repair.patch.gz Hellooooooooooo !! Well, this fixes the bug but it also means that the object that is pickled does not necessarily correspond to the original one, as the new one admits multiple edges What about setting Nathann |
comment:4
Hi! I think this is not the case because the DiGraph object is not used in the resulting tuple -- it is just a device to get all arcs. Maybe I don't understand it correctly, but I assume that allow_multiedges is pickled one level higher, in the SparseGraphBackend object.
What do you think? |
comment:5
Quite obviously that I said something stupid Give me a few seconds to give it a more attentive look Nathann |
comment:7
Hmmmm... You are totally right, your patch is good and sound. I do not explain why Sage's source code is written like that, but.... Thank you for this patch, and sorry for my stupid remark Nathann |
comment:8
Thanks for the fast review! The fix really looks like something everyone would try without any thinking. :-) Lukáš |
Reviewer: Nathann Cohen |
Author: Lukáš Lánský |
Merged: sage-5.0.beta3 |
Title says it all:
CC: @sagetrac-sage-combinat @nathanncohen @sagetrac-brunellus
Component: graph theory
Author: Lukáš Lánský
Reviewer: Nathann Cohen
Merged: sage-5.0.beta3
Issue created by migration from https://trac.sagemath.org/ticket/10916
The text was updated successfully, but these errors were encountered: