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
Exceptions when multiedges/loops are not supported #15572
Comments
Branch: u/ncohen/15572 |
New commits:
|
Commit: |
comment:2
Looks like Fixed ! Nathann |
Reviewer: elixyre |
Changed reviewer from elixyre to Jean-Baptiste Priez |
comment:6
Doctest failures:
|
comment:7
Sorry 'bout that. Just fixed it by updating the last commit. Nathann |
Changed commit from |
Commit: |
* develop: (59 commits) Updated Sage version to 6.1.beta4 trac sagemath#15572: DiGraph.is_directed_acyclic handles loops pretty well Fixed bug in uniform matroid. trac sagemath#15619: Pickling multigraphs with loops and labels Trac 15619: Review commit Trac 15603: More doctests, nicer error message No need to specify caller_name in verbose() Add comments, small cosmetic changes Make q monic before computing cubic resolvent Implement splitting fields for number fields trac sagemath#15619: bug in the former definition; exception to avoid it in the future trac 8723: fix one line in isogeny_small_degree Use "in" instead of PyDict_Contains() test for membership with `x in self`; minor doc formatting change trac sagemath#15619: Pickling of immutable graphs Rebased on sage-6.1.beta2 # User Thomas Feulner <thomas.feulner@uni-bayreuth.de> Implemented IntegerVectors_nk.rank(). Fixes sagemath#15609 Trac sagemath#5153: small change in documentation. Trac 7695: Variable name for all subfields where the name ends with a digit ...
Some Graph functions are not made to handle non-simple graphs, i.e. graphs containing loops or multiple edges. This ticket adds necessary exceptions from place to place, hoping no error remains ignored.
The exception advises the user to remove loops/multiple edges from his graph and try again (and to update the function if he thinks that not supporting non-simple graphs is a mistake)
:-P
This has been reported on sage-support fairly recently [1], and thousands of times before. Past time to deal with those wrong answers
:-/
[1] https://groups.google.com/d/msg/sage-support/bsXYMXwgW5w/LPrmCNGoah0J
CC: @sagetrac-azi @sagetrac-sage-combinat @nthiery @dcoudert
Component: graph theory
Author: Nathann Cohen
Branch/Commit: u/ncohen/15572 @
606221c
Reviewer: Jean-Baptiste Priez
Issue created by migration from https://trac.sagemath.org/ticket/15572
The text was updated successfully, but these errors were encountered: