Restrict matplotlib version check for failing test#12052
Conversation
Signed-off-by: Nathaniel Starkman (@nstarman) <[email protected]>
|
That is so weird. I don't understand why this is happening... Did they re-release 3.4.2 ?! How can the behavior change like this? |
|
Unless this somehow only affects the dev version... There is a vague memory of us not able to use dev tag for their version check. Which means this is going to come back and haunt us after every matplotlib release. 😢 |
|
Not sure about backporting... but doesn't hurt? #11717 was milestoned for 4.3. |
Perhaps a better fix would be to target the dev tag? Or check if it's a released version? |
|
@nstarman , that is worth looking into. The last time we had to do this, we couldn't due to matplotlib/matplotlib#19419 but I see that issue is now closed. |
Restrict matplotlib version check for failing test
|
I had to backport this to LTS in the end so updating the milestone |
Signed-off-by: Nathaniel Starkman (@nstarman) [email protected]
Restrict the version check to the relevant matplotlib version.
Fixes #12050
Checklist for package maintainer(s)
This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.
Extra CIlabel.no-changelog-entry-neededlabel.astropy-botcheck might be missing; do not let the green checkmark fool you.backport-X.Y.xlabel(s) before merge.