@manushree635 Thanks a lot for the PR. Can you tidy up a bit and add a descriptive title and link the issue in the description instead of the title? If you say "closes#19856" it will automatically close.

Without looking at the original issue, I suspect you will want to add a test so that this doesn't break in the future.

@manushree635 Thanks a lot for the PR. Can you tidy up a bit and add a descriptive title and link the issue in the description instead of the title? If you say "closes#19856" it will automatically close.

Without looking at the original issue, I suspect you will want to add a test so that this doesn't break in the future.

done

Thanks - this needs to pass the current test suite and preferably would have a new test.

This PR is affected by a re-writing of our history to remove a large number of accidentally committed filessee discourse for details.

To recover this PR it will need be rebased onto the new default branch (main). There are several ways to accomplish this, but we recommend (assuming that you call the matplotlib/matplotlib remote"upstream"

git remote updategit checkout maingit merge --ff-only upstream/maingit checkout YOUR_BRANCHgit rebase --onto=main upstream/old_master# git rebase -i main # if you prefergit push --force-with-lease# assuming you are tracking your branch

If you do not feel comfortable doing this or need any help please reach out to any of the Matplotlib developers. We can either help you with the process or do it for you.

Thank you for your contributions to Matplotlib and sorry for the inconvenience.

Hi@manushree635 - are you interested in continuing this work? Please let us know if you need help moving forward. Cheers!

Given this is very old with no response, and is made obsolete by#27576, I'm going to close. Thanks for opening!