Skip to content

Conversation

@mantepse
Copy link
Contributor

@mantepse mantepse commented Nov 9, 2025

See also #40935.

We do not deprecate spanning_trees_count, but we do not advertise it anymore.

@dcoudert
Copy link
Contributor

dcoudert commented Nov 9, 2025

There is a lint issue (unexpected white space).

@github-actions
Copy link

github-actions bot commented Nov 9, 2025

Documentation preview for this PR (built with commit e6fb3c4; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

Copy link
Contributor

@dcoudert dcoudert left a comment

Choose a reason for hiding this comment

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

LGTM.

@mantepse
Copy link
Contributor Author

mantepse commented Nov 9, 2025

Thank you! Maybe you could also have a look at #40939?

vbraun pushed a commit to vbraun/sage that referenced this pull request Nov 10, 2025
…g_trees for consistency

See also sagemath#40935.

We do not deprecate `spanning_trees_count`, but we do not advertise it
anymore.

URL: sagemath#41155
Reported by: Martin Rubey
Reviewer(s): David Coudert
vbraun pushed a commit to vbraun/sage that referenced this pull request Nov 11, 2025
sagemathgh-41155: replace spanning_trees_count with number_of_spanning_trees for consistency
    
See also sagemath#40935.

We do not deprecate `spanning_trees_count`, but we do not advertise it
anymore.
    
URL: sagemath#41155
Reported by: Martin Rubey
Reviewer(s): David Coudert
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.

2 participants