Skip to content
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

rename the backtrack algorithm of method longest_path with deprecation #36574

Merged
merged 9 commits into from
Dec 6, 2023

Conversation

dcoudert
Copy link
Contributor

Fixes #36530.

More precisely, we:

  • Rename algorithm "backtrack" as "heuristic" and add a deprecation warning
  • Raise an error when some parameters are used in combination with the "backtrack"/"heuristic" algorithm

📝 Checklist

  • The title is concise, informative, and self-explanatory.
  • The description explains in detail what this PR is about.
  • I have linked a relevant issue or discussion.
  • I have created tests covering the changes.
  • I have updated the documentation accordingly.

⌛ Dependencies

@dcoudert
Copy link
Contributor Author

@maxale

Copy link
Member

@mkoeppe mkoeppe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

The doctest failures appear unrelated (more trouble with nauty?)

@dcoudert
Copy link
Contributor Author

The doctest failures appear unrelated (more trouble with nauty?)

The same failures with nauty are reported by CI in #36682 which is independent from this PR. I don't know what's going on. It's not reporting that nauty is not available, but calls to nauty return nothing.

@vbraun vbraun force-pushed the develop branch 2 times, most recently from 883e05f to e349b00 Compare November 12, 2023 16:25
Copy link

github-actions bot commented Dec 3, 2023

Documentation preview for this PR (built with commit 5e6a0aa; changes) is ready! 🎉

vbraun pushed a commit to vbraun/sage that referenced this pull request Dec 4, 2023
…ath` with deprecation

    
Fixes sagemath#36530.

More precisely, we:
- Rename algorithm "backtrack" as "heuristic" and add a deprecation
warning
- Raise an error when some parameters are used in combination with the
"backtrack"/"heuristic" algorithm

### 📝 Checklist

<!-- Put an `x` in all the boxes that apply. -->
<!-- If your change requires a documentation PR, please link it
appropriately -->
<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
<!-- Feel free to remove irrelevant items. -->

- [x] The title is concise, informative, and self-explanatory.
- [x] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [x] I have created tests covering the changes.
- [x] I have updated the documentation accordingly.

### ⌛ Dependencies

<!-- List all open PRs that this PR logically depends on
- sagemath#12345: short description why this is a dependency
- sagemath#34567: ...
-->

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: sagemath#36574
Reported by: David Coudert
Reviewer(s): David Coudert, Matthias Köppe
@vbraun vbraun merged commit 8801f6e into sagemath:develop Dec 6, 2023
14 of 17 checks passed
@mkoeppe mkoeppe added this to the sage-10.3 milestone Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

.longest_path(algorithm='backtrack') gives incorrect result
3 participants