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

DOC: tweak wording on Figure.show warning#24607

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

Merged
timhoffm merged 3 commits intomatplotlib:mainfromtacaswell:doc/figshow
Dec 13, 2022

Conversation

tacaswell
Copy link
Member

PR Summary

closes#22169

PR Checklist

Documentation and Tests

  • Documentation is sphinx and numpydoc compliant (the docs shouldbuild without error).

@tacaswelltacaswell added this to thev3.6.3 milestoneDec 3, 2022
closesmatplotlib#22169Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
Comment on lines 2620 to 2621
Some, but not all, GUI toolkits will register an input hook on
import. See :ref:`cp_integration` for more details.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

My apologies, but I find these changes much more confusing than the original. What is an "input hook"? What is a "GUI toolkit", and why do they register an "input hook"? Where do they register it? and what does "on import" mean? On import of what?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Note that there is a typo in the previous paragraph "an GUI even loop"...

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It does include a link to the (much) longer explanation.

#22169 noted that they found a case where itdid work. The goal was to add a few more details about when you should expect this to work or not.


If you're in a shell without input hook integration or executing a
python script, you should use `matplotlib.pyplot.show` with
``block=True`` instead, which takes care of starting and running
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

block=True is the default?

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The default depends on if we are in "interactive mode" or not.

Co-authored-by: Oscar Gustafsson <oscar.gustafsson@gmail.com>
Co-authored-by: Jody Klymak <jklymak@gmail.com>
@timhoffmtimhoffm merged commit666c7e3 intomatplotlib:mainDec 13, 2022
@QuLogic
Copy link
Member

meeseeksdev backport to v3.6.x

meeseeksmachine pushed a commit to meeseeksmachine/matplotlib that referenced this pull requestDec 13, 2022
QuLogic added a commit that referenced this pull requestDec 14, 2022
…607-on-v3.6.xBackport PR#24607 on branch v3.6.x (DOC: tweak wording on Figure.show warning)
@ksundenksunden mentioned this pull requestFeb 20, 2023
6 tasks
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@jklymakjklymakjklymak left review comments

@timhoffmtimhoffmtimhoffm approved these changes

@oscargusoscargusoscargus left review comments

@dstansbydstansbydstansby approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v3.6.3
Development

Successfully merging this pull request may close these issues.

[Doc]: figure.show works beyond what is documented
6 participants
@tacaswell@QuLogic@jklymak@timhoffm@dstansby@oscargus

[8]ページ先頭

©2009-2025 Movatter.jp