search

AdamOswald / tes

2 stars 1 forks source link

Update dependency matplotlib to v3.7.1 - autoclosed #118

Closed renovate[bot] closed 1 year ago

renovate[bot] commented 1 year ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
matplotlib (source) ==3.6.2 -> ==3.7.1 age adoption passing confidence

Release Notes

matplotlib/matplotlib ### [`v3.7.1`](https://togithub.com/matplotlib/matplotlib/releases/tag/v3.7.1): REL: v3.7.1 [Compare Source](https://togithub.com/matplotlib/matplotlib/compare/v3.7.0...v3.7.1) This is the first bugfix release of the 3.7.x series. This release contains several bug-fixes and adjustments: - Ensure Qhull license is included in binary wheels - Fix application of rcParams on Axes labels - Fix compatibility with Pandas datetime unit converter - Fix compatibility with latest GTK4 - Fix import of styles with relative path - Fix Lasso unresponsiveness when clicking and immediately releasing - Fix pickling of draggable legends - Fix RangeSlider.set_val when new value is outside existing value - Fix size of Tk spacers when changing display DPI - Fix wrapped text in constrained layout - Improve compatibility with third-party backends - Improve error if animation save path does not exist ### [`v3.7.0`](https://togithub.com/matplotlib/matplotlib/releases/tag/v3.7.0): REL: v3.7.0 [Compare Source](https://togithub.com/matplotlib/matplotlib/compare/v3.6.3...v3.7.0) Highlights of this release include: - Plotting and Annotation improvements - `hatch` parameter for pie - Polar plot errors drawn in polar coordinates - Additional format string options in `~matplotlib.axes.Axes.bar_label` - `ellipse` boxstyle option for annotations - The *extent* of `imshow` can now be expressed with units - Reversed order of legend entries - `pcolormesh` accepts RGB(A) colors - View current appearance settings for ticks, tick labels, and gridlines - Style files can be imported from third-party packages - Improvements to 3D Plotting - 3D plot pan and zoom buttons - *adjustable* keyword argument for setting equal aspect ratios in 3D - `Poly3DCollection` supports shading - rcParam for 3D pane color - Figure and Axes Layout - `colorbar` now has a *location* keyword argument - Figure legends can be placed outside figures using constrained_layout - Per-subplot keyword arguments in `subplot_mosaic` - `subplot_mosaic` no longer provisional - Widget Improvements - Custom styling of button widgets - Blitting in Button widgets - Other Improvements - Source links can be shown or hidden for each Sphinx plot directive - Figure hooks - New & Improved Narrative Documentation - Brand new :doc:`Animations ` tutorial. - New grouped and stacked `bar chart <../../gallery/index.html#lines_bars_and_markers>`\_ examples. - New section for new contributors and reorganized git instructions in the :ref:`contributing guide`. - Restructured :doc:`/tutorials/text/annotations` tutorial. ### [`v3.6.3`](https://togithub.com/matplotlib/matplotlib/releases/tag/v3.6.3): REL: v3.6.3 [Compare Source](https://togithub.com/matplotlib/matplotlib/compare/v3.6.2...v3.6.3) This is the third bugfix release of the 3.6.x series. This release contains several bug-fixes and adjustments: - Fix Artist removal from `axes_grid1` Axes classes - Fix `inset_locator` in subfigures - Fix `scatter` on masked arrays with units - Fix colorbar ticks with log norm contours - Fix deprecation warnings in GTK4 backend - Fix using relative paths in `HTMLWriter` - Improve failure message from rcParams string validation for tuple inputs - Improve performance of QtAgg backends - No longer modify `pil_kwargs` argument to `imsave` and `savefig`

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Mend Renovate. View repository job log here.

viezly[bot] commented 1 year ago

Pull request by bot. No need to analyze

performance-testing-bot[bot] commented 1 year ago

Unable to locate .performanceTestingBot config file

difflens[bot] commented 1 year ago

View changes in DiffLens

guide-bot[bot] commented 1 year ago

Thanks for opening this Pull Request! We need you to:

  1. Fill out the description.

    Action: Edit description and replace <!- ... --> with actual values.

  2. Complete the activities.

    Action: Complete If you want to rebase/retry this PR, check this box

    If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

difflens[bot] commented 1 year ago

View changes in DiffLens

difflens[bot] commented 1 year ago

View changes in DiffLens

difflens[bot] commented 1 year ago

View changes in DiffLens

difflens[bot] commented 1 year ago

View changes in DiffLens

difflens[bot] commented 1 year ago

View changes in DiffLens

pull-request-quantifier-deprecated[bot] commented 1 year ago

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : No Changes Size : +0 -0 Percentile : 0% Total files changed: 1 Change summary by file extension: .txt : +0 -0 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

difflens[bot] commented 1 year ago

View changes in DiffLens