-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle multiple C{type} in an epytext docstring #7
Comments
Damn, I didn't even know this was a thing we supported. I thought we only stripped backticks |
Maybe we don't and it's a fluke that it works this way. I'm pretty sure it's made up syntax. I've never been able to find anything else using it. |
Hmmm I'm actually not able to reproduce this. Here's what I get when I tested. It reads as the RestParser and writing with GoogleWriter produces:
I wonder if your version is custom and has this added as an additional feature? I vaguely remember maybe you or Andy adding this in? I wonder if we decided to not include that in the open source release? |
I can't reproduce either, even on the original docstring that I saw the issue on... So I'm happy to close this I did however find that the |
Huh funky. I'm cool to support converting that syntax as a feature request if you think its useful. |
It's part of epytext and it's used a lot in our codebases. It would be useful for docconvert to support their conversion. |
I've reopened this is as the feature request to convert |
Probably way way too late for you to benefit from this, but finally added support for this |
Reading the following docstring
results in the following Google docstring
It looks like something is greedily looking for
C{}
but it needs to be more conservative.The text was updated successfully, but these errors were encountered: