Fix numpy docstring example parsing #104
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The numpy example parsing didn't seem to work the way numpy examples are formatted in the real-world. The assumption is that they look like this:
However, the correct interpretation is:
If descriptions are used, they go before the snippet:
It is also possible to have continuation marks after the initial Python prompt:
The code in this PR changes the way that numpy examples are parsed to allow for these changes, so it is a breaking change.