Docstrings with SQL-like words in them break highlighting

[birdonfire]

There's a problem with the syntax highlighting when viewing this file: https://github.com/18F/rdbms-subsetter/blob/master/subsetter.py

Something in the docstring at the top of the document is causing the problem. Perhaps something to do with the RST markup?

The syntax highlighting on the GitHub page suffers the same problem.

There are no actual syntax errors in the document, and the application code runs just fine.

SublimeText's highlighter renders it fine.

[birdonfire]

If I lower-case the word "INSERTS" on line 43, it totally fixes the highlighting.

[birdonfire]

It seems that the highlighter interprets the upper case INSERTS as the beginning of a SQL block that isn't then closed.

<div class="line cursor-line" data-screen-row="42">
    <span class="source python">
        <span class="string quoted double block sql python">
            rdbms-subsetter only performs the
            INSERTS; it
            <span class="string quoted single sql">
                <span class="punctuation definition string begin sql">'</span>
                s your responsibility to set
            </span>
        </span>
    </span>
    <span class="invisible-character">¶</span>
</div>

If I lower-case INSERTS, this block now looks like:

<div class="line cursor-line" data-screen-row="42">
    <span class="source python">
        <span class="string quoted double block sql python">
            rdbms-subsetter only performs the inserts; it's your responsibility to set
        </span>
    </span>
    <span class="invisible-character">¶</span>
</div>

[amlinger]

I'm experiencing the same issue, where we are extracting docstrings for usage in our API documentation, and therefore we are using markdown formatting inside the docstrings:

"""Delete Resource
`DELETE http://some-url.com/resource`
"""
def destroy(self):
    pass

Which messes up the rest of the file (and here as well, where I expected pass to be highlighted, and DELETE not to be).

To me it seems as the rule named string.quoted.double.block.sql.python is the cause of this behaviour, and I've been fiddling around with it for a while but haven't really understood the grammar definitions yet.

It seems as the rule accepts additional characters apart from only whitespace between the intial """ specified by begin, and the beginning of the SQL statement specified by the keywords + whitespace, but have not come any farther than that.

[hvdklauw]

Any progress on this?

I just ran into the same problem.

Seems the syntax file starts the SQL context and only closes it when it encounters three double quotes, which basically eats them and leaves nothing for the commend to be closed.

[morenoh149]

I'm getting this for DELETE as well

):
    '''
    Accounts
    ###**Actions**:
      - `GET /:id/card`
      - `POST /:id/card`
      - `PUT /:id/`
      - `DELETE /:id/`
    '''
    serializers = {

highlights everything from Accounts to the end of the file.