Thank you for your willingness to contribute. Did you intend to link a different issue? The one you linked is not about text in an axes.

Also please fill out the PR summary using our template and ensure the tests pass.

⏰ This pull request might be automatically closed in two weeks from now.

Thank you for your contribution to Matplotlib and for the effort you have put into this PR. This pull request does not yet meet the quality and clarity standards needed for an effective review. Project maintainers have limited time for code reviews, and our goal is to prioritize well-prepared contributions to keep Matplotlib maintainable.

Matplotlib maintainers cannot provide one-to-one guidance on this PR. However, if you ask focused, well-researched questions, a community member may be willing to help. 💬

To increase the chance of a productive review:

• Use the template provided in the PR description and fill it out as completely as possible, especially the summary and AI Disclosure sections.
• Make sure your PR conforms to our PR checklist.

As the author, you are responsible for driving this PR, which entails doing necessary background research as well as presenting its context and your thought process. If you are a new contributor, or do not know how to fulfill these requirements, we recommend that you familiarize yourself with Matplotlib's development conventions or engage with the community via our Discourse or one of our meetings before submitting code.

If you substantially improve this PR within two weeks, leave a comment and a team member may remove the status: autoclose candidate label and the PR stays open. Cosmetic changes or incomplete fixes will not be sufficient. Maintainers will assess improvements on their own schedule. Please do not ping (@) maintainers.

Thanks for the feedback.

I’ll update the PR summary/template and verify whether the linked issue is correct.

I’ll also investigate the failing tests and push fixes shortly.

@rcomer Thank you for the clarification. I have opened a new issue #31635
which correctly describes the bug this PR fixes — when ax.text()
is used with wrap=True inside an axes, wrapping incorrectly uses
the figure boundary instead of the axes boundary, causing text to
overflow outside the axes. I have updated the PR description accordingly.

The rstcheck precommit failure is a pre-existing issue in the repo —
doc/users/getting_started/index.rst references a file
/install/quick_install.inc.rst that does not exist. This is unrelated
to my changes and can be verified by checking the same error on other
recent PRs.

The AppVeyor Windows CI failure is an infrastructure issue — micromamba
failed to parse its history file and crashed during dependency installation
(line 1929: Command exited with code 1). Tests never ran as a result.
This is unrelated to my changes.

@rcomer Thanks for the clarification.

I understand the current behavior is consistent with the documented implementation of set_wrap.

I’ve updated the PR to frame this as an optional axes-aware wrapping enhancement while preserving existing default behavior for backward compatibility.

@codegnan-dm before taking this PR further, please could you open an issue feature request describing your use case? I.e., what do you use Matplotlib for and why do you want this?

@rcomer I have opened a feature request issue #31655 describing my use case.

I use matplotlib for creating multi-axes figures such as dashboards and
subplot-based reports. When adding long text annotations inside narrow axes
using ax.text() with wrap=True, the text overflows into adjacent axes because
wrapping uses the figure boundary instead of the axes boundary.

The fix in this PR adds optional axes-aware wrapping — when text belongs to
an axes, it wraps within the axes boundary. When text is directly on a figure
(e.g. suptitle), it falls back to the figure boundary as before. This preserves
full backward compatibility.

Issue: #31655

In particular why does the top centered text wrap after every word.

I suspect that needs #31546, but I haven't checked.

I haven't analyzed the bottom left case

That one is positioned outside the axes at (-1, 0). I do not think wrapping to the axes makes sense in that case.

I think this should get a test for axes title as I think that would be a very common use case that is currently broken by this PR.

import matplotlib.pyplot as plt

fig, ax = plt.subplots(figsize=(3, 3), layout='constrained')
ax.set_title('axes title that is too long for the size', wrap=True)

plt.show()

main

this PR

Superseded by #31716 which implements the design agreed upon in issue #31655 — supporting wrap='axes' and wrap='figure' as string values.