| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
…olor To solve this, we needed to ensure that the caps would use the specified ecolor independently of the global mpl.rcParams['lines.markeredgecolor']. This was achieved by setting the marker edge color for the caps separately, rather than relying on the global configuration.
|
The default value of lines.markeredgecolor 'auto' which means "follow the color", but when setting it to a color it stops following the color of the line. This is the correct fix. |
Sorry, something went wrong.
|
@useidemaisachola Thank you for this fix and the test! If you can clean up the linting/whitespace issues I think this can be merged straight away. |
Sorry, something went wrong.
|
@tacaswell ok, i can solve them! One question as this is my first PR - after i resolve the problems with the spaces i have to commit and open another PR? Or it's possible to still use this one? |
Sorry, something went wrong.
|
You should continue on your branch, and pushing it here will update this PR. |
Sorry, something went wrong.
|
@tacaswell I resolved the problem with the spaces! Now it's giving some kind of error with the version of python on windows... It is something that i have to change? |
Sorry, something went wrong.
|
@useidemaisachola that Azure Windows test can be flakey. The failure is not caused by your change. I have re-run it to see if we can be lucky the second time. |
Sorry, something went wrong.
|
so, now i have to resolve the conflits? |
Sorry, something went wrong.
Yes, but if you are not comfortable doing that we can handle it for you. It looks like you and and another recent PR have added new tests in the same place, so it's just a case of making sure we keep both. |
Sorry, something went wrong.
|
Already resolved the conflit but I guess i leaved an extra line at the end of the file or something like that, because it's failing one test... it's that? |
Sorry, something went wrong.
|
I took the liberty to remove the extra line at the end. Tests should pass now. |
Sorry, something went wrong.
| y = np.sin(x) | ||
| yerr = 0.1 | ||
| mpl.rcParams['lines.markeredgecolor'] = 'green' | ||
|
|
||
| fig, ax = plt.subplots() | ||
| errorbars = ax.errorbar(x, y, yerr=yerr, fmt='o', capsize=5) |
There was a problem hiding this comment.
As above:
| y = np.sin(x) | |
| yerr = 0.1 | |
| mpl.rcParams['lines.markeredgecolor'] = 'green' | |
| fig, ax = plt.subplots() | |
| errorbars = ax.errorbar(x, y, yerr=yerr, fmt='o', capsize=5) | |
| mpl.rcParams['lines.markeredgecolor'] = 'green' | |
| fig, ax = plt.subplots() | |
| errorbars = ax.errorbar(x, np.sin(x), yerr=0.1) |
Sorry, something went wrong.
|
ok, thank you for the tips and the help! |
Sorry, something went wrong.
|
I have to enter the suggestion that you told me or it´s already changed in the repository? |
Sorry, something went wrong.
|
You'll have to apply it yourself, either locally and push, or using the UI here. |
Sorry, something went wrong.
Co-authored-by: Tim Hoffmann <2836374+timhoffm@users.noreply.github.com>
|
ok, it gave an error but I will fix it. |
Sorry, something went wrong.
|
I think everything it´s ok now. |
Sorry, something went wrong.
|
Now i have to do close or something like that? |
Sorry, something went wrong.
|
No. You don't have to do anything. We have policy that each PR needs two approvals by core developers. So, we're just waiting for a second review. |
Sorry, something went wrong.
|
Ok, thank you. |
Sorry, something went wrong.
|
Thanks @useidemaisachola! Congratulations on your first PR to Matplotlib 🎉 We hope to hear from you again. |
Sorry, something went wrong.
|
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
git checkout v3.10.x git pull
git cherry-pick -x -m1 20bdd72d3cb9a4a93657091d80fdeb9d0089609c
git commit -am "Backport PR #29895: The 'lines.markeredgecolor' now doesn't interfere on the color of errorbar caps "
git push YOURFORK v3.10.x:auto-backport-of-pr-29895-on-v3.10.x
And apply the correct labels and milestones. Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon! Remember to remove the Still Needs Manual Backport label once the PR gets merged. If these instructions are inaccurate, feel free to suggest an improvement. |
Sorry, something went wrong.
|
@QuLogic Thank you so much! So can I delete already the branch? The lumberbot gave some kind of feedback... |
Sorry, something went wrong.
|
@useidemaisachola you can safely delete your branch. Your work is now in Matplotlib's main branch and lumberbot is here to help us get it also into our v3.10.x branch (which we will use for the next micro release). |
Sorry, something went wrong.
|
Ok, thank you! |
Sorry, something went wrong.
… interfere on the color of errorbar caps
…3.10.x Backport PR #29895 on branch v3.10.x (The 'lines.markeredgecolor' now doesn't interfere on the color of errorbar caps)"
… interfere on the color of errorbar caps
| Back | FazBrowse Home | New Git URL |
PR summary
-This change was necessary to resolve a bug: Fixes #29780
-Color of errorbar caps now it's not affected by 'lines.markeredgecolor'.
The initial issue arose when the caps of the error bars were unintentionally adopting the color red, which was set globally in mpl.rcParams under the 'lines.markeredgecolor' parameter. This global setting was being applied to all markers, including the caps of error bars, causing the caps to appear red even when that wasn't intended.
The root cause of the problem was that the marker edge color defined globally (mpl.rcParams['lines.markeredgecolor']) was being inherited by the caps as part of the error bar plot. This caused the color of the caps to match the global red color, even when only the error bars were supposed to be red (through the ecolor parameter).
To solve this, we needed to ensure that the caps would use the specified ecolor independently of the global mpl.rcParams['lines.markeredgecolor']. This was achieved by setting the marker edge color for the caps separately, rather than relying on the global configuration.
The files that suffered alterations were _axes.py and test_axes.py.
PR checklist