This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eli.bendersky
Recipients docs@python, eli.bendersky
Date 2011-10-21.09:20:20
SpamBayes Score 0.0057248925
Marked as misclassified No
Message-id <1319188821.69.0.880362595614.issue13239@psf.upfronthosting.co.za>
In-reply-to
Content
The relevant code in Parser/parsetok.c is:

#ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD
        if (type == NOTEQUAL) {
            if (!(ps->p_flags & CO_FUTURE_BARRY_AS_BDFL) &&
                            strcmp(str, "!=")) {
                err_ret->error = E_SYNTAX;
                break;
            }
            else if ((ps->p_flags & CO_FUTURE_BARRY_AS_BDFL) &&
                            strcmp(str, "<>")) {
                err_ret->text = "with Barry as BDFL, use '<>' "
                                "instead of '!='";
                err_ret->error = E_SYNTAX;
                break;
            }
        }
#endif


Hmm... I'm too new to remember this joke, but here it presents a practical problem - since Grammar/Grammar is being directly reflected into the documentation (.. literalinclude:: ../../Grammar/Grammar) and thus can confuse.

Is it safe to just remove the whole thing from Grammar/Grammar and correspondingly Parser/parsetok.c ?
History
Date User Action Args
2011-10-21 09:20:21eli.benderskysetrecipients: + eli.bendersky, docs@python
2011-10-21 09:20:21eli.benderskysetmessageid: <1319188821.69.0.880362595614.issue13239@psf.upfronthosting.co.za>
2011-10-21 09:20:21eli.benderskylinkissue13239 messages
2011-10-21 09:20:20eli.benderskycreate