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

sage.plot: Update # needs, doctest cosmetics; fix sig_on_count doctest dataflow warnings #36950

Merged
merged 15 commits into from
Dec 26, 2023

Conversation

mkoeppe
Copy link
Contributor

@mkoeppe mkoeppe commented Dec 23, 2023

Fixes #36920

In part cherry picked from:

📝 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

@mkoeppe mkoeppe self-assigned this Dec 23, 2023
@mkoeppe mkoeppe changed the title sage.plot: Update # needs, doctest cosmetics sage.plot: Update # needs, doctest cosmetics; fix sig_on_count doctest dataflow warnings Dec 23, 2023
Copy link

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

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.

With theses changes, I don't observe the sig_on_count warnings anymore (tested on macOS).

LGTM.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Dec 23, 2023

Thanks for the review!

vbraun pushed a commit to vbraun/sage that referenced this pull request Dec 24, 2023
…ix `sig_on_count` doctest dataflow warnings

    
<!-- ^^^^^
Please provide a concise, informative and self-explanatory title.
Don't put issue numbers in there, do this in the PR body below.
For example, instead of "Fixes sagemath#1234" use "Introduce new method to
calculate 1+1"
-->
<!-- Describe your changes here in detail -->
Fixes sagemath#36920

<!-- Why is this change required? What problem does it solve? -->
<!-- If this PR resolves an open issue, please link to it here. For
example "Fixes sagemath#12345". -->
In part cherry picked from:
- sagemath#35095
<!-- If your change requires a documentation PR, please link it
appropriately. -->

### 📝 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.
- [ ] The description explains in detail what this PR is about.
- [x] I have linked a relevant issue or discussion.
- [ ] I have created tests covering the changes.
- [ ] 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: ...
-->
- Depends on sagemath#36905 (merged here)

<!-- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
    
URL: sagemath#36950
Reported by: Matthias Köppe
Reviewer(s): David Coudert
@vbraun vbraun merged commit f06727c into sagemath:develop Dec 26, 2023
20 of 22 checks passed
@mkoeppe mkoeppe added this to the sage-10.3 milestone Dec 26, 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.

Spurious warnings about optional tags
3 participants