> > I don't think this should be a problem, but current policy is to first >> deprecate it for a while (usually I've heard one year, see also #13109 for >> something that will hopefully work in the future). Presumably you can >> change the backend but still return the weights for now, and make it really >> clear what code would be deleted once the deprecation period was over? >> >
How does one exactly do this in these cases? The sage method is just a wrapper for networkx one that changed. I don't believe patching NetworkX source reverting it to the old inconsistent behavior is a good idea. In this case, since NetworkX is pure python I guess can just copy the old code under the sage method, but that doesn't seem like a clean solution. What would we do if the offending component were not python code? J -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
