Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Merge matplotlib changes #1

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

Open
wants to merge 10,000 commits into
base: master
Choose a base branch
from
Open

Merge matplotlib changes #1

wants to merge 10,000 commits into from

Conversation

ligon
Copy link
Owner

@ligon ligon commented Apr 24, 2020

No description provided.

deep-jkl and others added 30 commits September 21, 2021 23:37
Apply suggestion from @timhoffm, update lib/matplotlib/markers.py

Co-authored-by: Tim Hoffmann <[email protected]>
Fix clim handling for pcolor{,mesh}.
Fix format_cursor_data with nans.
Fix DATA_PARAMETER_PLACEHOLDER interpolation for quiver&contour{,f}.
... and small local cleanups.
- Use finite differences to estimate derivative rather than splines
  (which are conceptually much more complicated).
- Include a "constant error" case, which shows that the band does have
  constant width in that case.
- Force the axes aspect to 1 (so that constant width actually appears
  constant).
- Use np.full() to set up the codes array.
The pixel-sized marker previously use (",") was so small that it looked
more like a rendering artefact than an actual data point.
The error messages now provide better instruction on how to fix the
problem.

There are some paths we can not split (one with hatching, fills, or
that claim they can not be simplified) so tell user that.

If we could have otherwise split up the path if the chunksize is set
to less than 100, which disables the feature, ask user to make it
bigger or make the path simplification more aggressive.

If the chunksize is bigger than the data, ask user to make it smaller
or make the path simplification more aggressive.

If the chunksize is smaller than the data, but still too big ask user
to make it smaller or make the path simplification more aggressive.

closes #19325

Co-authored-by: Antony Lee <[email protected]>
This allows longer, more textured, paths to be drawn with the default
settings at the risk of very long run times.
- Make sure values are be big enough / small enough
- make long path test more pathological (Random data will sometimes go in the
  same direction)
This prevents them accidentally breaking the test runner itself,
depending on platform.
DOC: Increase marker size in double_pendulum example.
DOC: Improve curve_error_band example.
DOC: Docstring cleanups around DATA_PARAMETER_PLACEHOLDER.
MNT: Simplify argument parsing in stem().
timhoffm and others added 28 commits October 14, 2021 20:03
DOC: move usage tutorial info to Users guide rst
Inherit more docstrings.
Simplify _init_legend_box.
ENH: Add support to save images in WebP format
Simplify wording of allowed errorbar() error values
Add GHA testing whether files were added and deleted in the same PR.
The exception message is clearer for end users than downstream callers
failing to `open()` a file named `""`.

Also update the function's docstring.

_tfmfile now never returns None (an exception would have been raised
earlier by find_tex_file), so remove the corresponding branch.
Raise an exception when find_tex_file fails to find a file.
Co-authored-by: Tim Hoffmann <[email protected]>
Describe possible need for loading the 'lmodern' package when using PGF files
Currently, the scatter_hist example needs to force the main axes to be
square by carefully adjusting the figure size -- shared axes and fixed
aspects don't work well together (and manually resizing the figure shows
that the aspect is indeed not fixed).  In fact, the
scatter_hist_locatable_axes example explicitly states that the advantage
of using axes_grid1 is to allow the aspect to be fixed.

I realized that one can also use inset_axes to position the marginals
axes relative to the main axes *and* support a fixed aspect ratio for
the main axes.  Perhaps this can be considered as a slight API abuse,
but I think this is a solution for a real limitation; the question is
whether we want to promote this use?
Demonstrate inset_axes in scatter_hist example.
We don't need to drop the alpha channel for jpeg anymore as imsave
handles that.

In imsave, also clarify that `sm` is not going to be used in the
already-usable-rgba case.

Also, spliting out pil_kwargs under "other parameters" seems overkill
for an effectively internal method (`savefig` is the user-facing API).
Enable tests for text path based markers
Document what indexing a GridSpec returns
Factor common parts of saving to different formats using pillow.
Log pixel coordinates in event_handling coords_demo example on terminal/console
@tacaswell tacaswell deleted the branch ligon:master October 20, 2021 19:53
@tacaswell tacaswell deleted the master branch October 20, 2021 19:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.