-
-
Notifications
You must be signed in to change notification settings - Fork 488
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
IncidenceStructure breaks if points cannot be sorted #26938
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:4
A mix of points of strings type and integers type will not make this function fail. This work in python3:
The comparison stops if the first element of each tuple are different. |
comment:5
Indeed, pep8 says so, my bad. |
comment:7
On #22029, I do get
and it's pointing to the line
|
This comment has been minimized.
This comment has been minimized.
Author: Jeroen Demeyer |
Commit: |
New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:11
ok, let it be |
Reviewer: Frédéric Chapoton |
comment:12
Retarging tickets optimistically to the next milestone. If you are responsible for this ticket (either its reporter or owner) and don't believe you are likely to complete this ticket before the next release (8.7) please retarget this ticket's milestone to sage-pending or sage-wishlist. |
Changed branch from u/jdemeyer/incidencestructure_breaks_if_points_cannot_be_sorted to |
This sort can fail if the points are not comparable:
The
sortkey
tries to find a clever way to "sort" the points but hardcoding classes like that is not a general solution. In particular, it's still comparing integers and strings when #22029 is appplied.Instead, just don't sort.
CC: @vinklein
Component: combinatorics
Author: Jeroen Demeyer
Branch/Commit:
a354dc1
Reviewer: Frédéric Chapoton
Issue created by migration from https://trac.sagemath.org/ticket/26938
The text was updated successfully, but these errors were encountered: