Skip to content

rename/deprecate bbox kwarg/property on Text #4990

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
tacaswell opened this issue Aug 26, 2015 · 2 comments
Closed

rename/deprecate bbox kwarg/property on Text #4990

tacaswell opened this issue Aug 26, 2015 · 2 comments
Labels
API: consistency Documentation status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action topic: text

Comments

@tacaswell
Copy link
Member

As discussed in #4942 (comment) the 'bbox' kwarg/property is confusing. Most places in mpl 'bbox' means 'the bounding box that the artists falls with in' where as in this case it is properties to go with a background patch behind the text artist.

@tacaswell tacaswell added this to the proposed next point release milestone Aug 26, 2015
@WeatherGod
Copy link
Member

I am +1 on rename (through a deprecation cycle). But this could probably be
immediately addressed by simple docstring.

On Tue, Aug 25, 2015 at 10:36 PM, Thomas A Caswell <notifications@github.com

wrote:

As discussed in #4942 (comment)
#4942 (comment)
the 'bbox' kwarg/property is confusing. Most places in mpl 'bbox' means
'the bounding box that the artists falls with in' where as in this case it
is properties to go with a background patch behind the text artist.


Reply to this email directly or view it on GitHub
#4990.

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Oct 3, 2017
Copy link

github-actions bot commented Nov 3, 2023

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Nov 3, 2023
@github-actions github-actions bot added the status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. label Dec 4, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API: consistency Documentation status: closed as inactive Issues closed by the "Stale" Github Action. Please comment on any you think should still be open. status: inactive Marked by the “Stale” Github Action topic: text
Projects
None yet
Development

No branches or pull requests

3 participants