| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
There was already an attempt of making the block argument explicit in #11170 It didn't work out for some reason. Maybe it'll help to get it straight here though. |
Sorry, something went wrong.
| non-interactive to interactive mode (not recommended). In | ||
| that case it displays the figures but does not block. | ||
| Mainly used in non-interactive mode to draw and display | ||
| the figures. It usually does nothing in interactive mode. |
There was a problem hiding this comment.
Why would it not do anything in interactive mode? I think it also shows the figure there.
Sorry, something went wrong.
There was a problem hiding this comment.
I am not sure. It was written in the old docstring that it does nothing.
When I test it in spyder, the only difference is that the "thumbnail" in the toolbar start to blink if plt.show() is used. The figure window don't pop up to the front or something like that.
Sorry, something went wrong.
|
I didn't know about #11170. It doesn't seems clear what happens when reading that though. So the problem might be in one or several backends? |
Sorry, something went wrong.
|
It looks like the exact same issue in the failing tests, if I recall that correctly, which is about the WebAgg backend. See https://github.com/matplotlib/matplotlib/pull/11170/files#r186467036. |
Sorry, something went wrong.
|
Yes, the WebAgg doesn't seem to work but isn't it solved by the the line that tacaswell comment? I try that now. I don't know much about the different backends and how the backend class hierarchy works but to me it seems that the problem is that the show in backend bases take a keyword block but that this function is overridden in the WebAgg class with a show that takes no arguments. WebAgg is taken care of in the backend_bases show. |
Sorry, something went wrong.
| ---------- | ||
|
|
||
| block : bool or None | ||
| True means that the execution is blocked until the figures are closed |
There was a problem hiding this comment.
Can be shortend: "Whether the execution is blocked until the figures are closed."
Sorry, something went wrong.
There was a problem hiding this comment.
Alternative suggestion:
If True, the execution is blocked until all displayed figures are closed. If False, the python execution continues after the figures are displayed.
Sorry, something went wrong.
| and False means that the python execution continues after the figures | ||
| are displayed. | ||
|
|
||
| The default behavior is different in interactive and non-interactive |
There was a problem hiding this comment.
Shorter:
The default is True unless interactive mode is enabled or %matplotlib_ is used in IPython.
Sorry, something went wrong.
There was a problem hiding this comment.
Wouldn't want to go for the long version here. It's just redundant and doesn't add to the clarity.
Sorry, something went wrong.
|
I added a simple test of the input but I am not sure about the docstrings suggestions (or my own versions for that matter). I think that the explaination in the docstring that was suggested where to short. |
Sorry, something went wrong.
|
I think that my docstring proposals contain the same amount of information, they are just less verbose. But a third opinion would be good. |
Sorry, something went wrong.
|
A third opinion was being asked for: I can confirm that the two proposed changes by @timhoffm do indeed contain the same information. |
Sorry, something went wrong.
|
This has been superseeded by
@fredrik-1 sorry this stalled. Anyway, thanks for the contribution. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Rewrote the pyplot.show docstring and made the single kwarg block explicit.
Are the block keyword still experimental?