Open terencehonles opened 3 years ago
I didn't look at the code too closely, but it may make sense to see if these can surfaced as warnings which would still fail with twine check --strict
but would not prevent the rST from rendering. I had made the change on GitHub since it silently would drop documentation examples and it appears that's the same for PyPI, but since twine check
and possibly others consume this library the unknown options could possibly still be passed up without blowing up.
@di not sure if you have any input on this, sorry to bother if you're the wrong person to ask.
Related to #160
This is the same as my PR https://github.com/github/markup/pull/1452 and it may make sense to incorporate other changes from GitHub's rST processing.