#19227: Graphs: DFS and broken distance-parameter
-------------------------------------+-------------------------------------
Reporter: jmantysalo | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jmantysalo/graphs__dfs_and_broken_distance_parameter|
89b7490bec7e28f1c63bb81603eeab69fefb4e65
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by jmantysalo):
* cc: vbraun (added)
Comment:
Replying to [comment:4 ncohen]:
> Err.. Given that it is is broken, that the output is architecture-
dependent, and that people may have a misleading idea about what it does,
why don't we just remove it? Volker repeats often enough that "we don't
need to deprecate bugs". I only hope that in this case we agree that it is
a bug (which isn't always the case when Volker uses that argument).
Vbraun added to CC.
I am not exactly sure what counts as a bug and what not. See #18944.
I think that somebody might have code that uses this, maybe even working
code (i.e. using DFS with `distance` only for trees). Can we give
deprecation warning AND raise and exception? Then the user would at least
know what has happened and why the code does not work any more.
Volker, #19197 contains some discussion about this; that is where Nathann
saw this bug.
--
Ticket URL: <http://trac.sagemath.org/ticket/19227#comment:5>
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.
