Is there anyway to check how pypi is going to interpret the updated strings (short of releasing as seeing what it does)?

@tacaswell apparently yes:https://packaging.python.org/guides/making-a-pypi-friendly-readme/#validating-restructuredtext-markup

twine check dist/*

ETA1 I think I'm accidentally gonna learn about packaging 😅
ETA2:

Checking dist\matplotlib-3.2.0rc2+1618.g1f13cc811.tar.gz: PASSED

Now to figure out how to automate that 😓

I'm going to merge this and then manually do the backport so I can (finally) get the 3.2.0 tag done.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.2.x$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 64ae32323f9d997c00bf36326dc1d4196618c7b1

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #16626: Updated Readme + Setup.py for PyPa'

4. Push to a named branch :

git push YOURFORK v3.2.x:auto-backport-of-pr-16626-on-v3.2.x

5. Create a PR against branch v3.2.x, I would have named this PR:

"Backport PR#16626 on branch v3.2.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free tosuggest an improvement.

I have done the backport locally, will push soon.

Manually backported via65a35ef