Skip to content

[ENH]: Angle Annotation #24217

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

Closed
story645 opened this issue Oct 19, 2022 · 7 comments
Closed

[ENH]: Angle Annotation #24217

story645 opened this issue Oct 19, 2022 · 7 comments

Comments

@story645
Copy link
Member

Problem

There is a lengthy example of how to annotate angles, including a custom class to do so, at https://matplotlib.org/devdocs/gallery/text_labels_and_annotations/angle_annotation.html. This class is now being used in #24145 because annotating arrows is kind of complex and also useful.

Proposed solution

I think the class should be pulled into the library so it can be more easily reused. This would involve

@jacoverster
Copy link
Contributor

I'd be willing to assist here as well @story645

@story645
Copy link
Member Author

Awesome! First we should see though if there's support from other maintainers or if other maintainers oppose this feature.

@jklymak
Copy link
Member

jklymak commented Oct 19, 2022

What does this do as the aspect ratio changes? The idea of an angle annotation seems pretty niche and fragile for the main library. Given our experience with arrows I'd be really really cautious about adding something half baked.

@timhoffm
Copy link
Member

timhoffm commented Oct 21, 2022

I very much have the same concerns as @jklymak. This seems complex and we should not add it if we're not confident that it's "just-works".

@timhoffm
Copy link
Member

timhoffm commented Feb 2, 2025

This is complex to get right. We won’t provide half-baked solutions. It’s niche and therefore we don’t send time on this. We would accept a PR if it addresses the above concerns.

@timhoffm timhoffm closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2025
@story645
Copy link
Member Author

story645 commented Feb 3, 2025

@timhoffm why are you closing an issue where you say we'd accept a PR that addresses the concerns of the issue?

@timhoffm
Copy link
Member

timhoffm commented Feb 3, 2025

This is complex and niche. We should not be doing this and I very much doubt anybody es will. So it’s not worth keeping it open. IMO for an issue to stay open, we should either want this to be done (even though it may be hard and not happen for a long time) or it’s acceptable to be included and there’s a realistic chance that somebody else will meaningfully contribute. Otherwise we just pile up more and more open issues that are not relevant for the future development. Open issues are a curation of the direction of the library. If somebody wants to contribute, and looks for a topic that, they are the place to go. I wouldn’t recommend anybody to work on this, there are much more meaningful topics.

1200 open issues are not helpful. Either we close more aggressively according to my above criteria or we have to better structure and prioritize them #28834.

I left the note for the unlikely case that somebody stumbles over the issue and solves it because they need it so that they are not discouraged from bringing up the topic again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants