Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Labels for PatchCollection do not show #23998#24042

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
emmamastro wants to merge3 commits intomatplotlib:mainfromemmamastro:emma's-branch

Conversation

emmamastro
Copy link

PR Summary

This is in response to Labels for PatchCollection Issue#23998. I added both the Handler for Patch collection class and the patch collection handler to the default_handler_map.

PR Checklist

Tests and Styling

  • [N/A ] Has pytest style unit tests (andpytest passes).
  • [N/A ] IsFlake 8 compliant (installflake8-docstrings and runflake8 --docstring-convention=all).

Documentation

  • [ N/A] New features are documented, with examples if plot related.
  • New features have an entry indoc/users/next_whats_new/ (follow instructions in README.rst there).
  • API changes documented indoc/api/next_api_changes/ (follow instructions in README.rst there).
  • Documentation is sphinx and numpydoc compliant (the docs shouldbuild without error).

@oscargusoscargus linked an issueSep 29, 2022 that may beclosed by this pull request
@oscargus
Copy link
Member

oscargus commentedSep 29, 2022
edited
Loading

Thanks you! As you noted in#23998 there was already another PR opened. It is not clear which will be merged (although most likely we go with the first if that gets up to shape), but in case you want to complete this one, what is additionally required is a test. This is discussed further in#24028 as it is missing there as well.

Also, there are a number of linting failures.

Finally, in general we prefer to not merge the main branch into a PR, but to rebase the PR onto the main branch. In your case you can do something like (in your branchemma's-branch)

git rebase -i main# An editor will pop up, remove the line with the merge, save and closegit log# Confirm that you only have the two commits with your changes as the two last onesgit push origin emma's-branch --force-with-lease

(You can also usegit rebase -i main and selectfixup to get the number of commits down, usually a single commit is preferred/enough for a PR.)

Edit: note that you probably donot want tofixup the merge commit as that may completely break things.

@jklymak
Copy link
Member

I'll close this as a duplicate. Please work in the context of the original PR. Thanks for your contribution!

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Labels for PatchCollection do not show
4 participants
@emmamastro@oscargus@jklymak@timhoffm

[8]ページ先頭

©2009-2025 Movatter.jp