➜

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.

classification
Title: #if 0 block on parsetok.c
Type: Stage: resolved
Components: Versions: Python 3.9
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: eamanu
Priority: normal Keywords: patch

Created on 2019-11-24 00:53 by eamanu, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Pull Requests
URL Status Linked Edit
PR 17365 merged eamanu, 2019-11-24 00:59
Messages (1)
msg357387 - (view) Author: Emmanuel Arias (eamanu) * Date: 2019-11-24 00:53 
Hi, 

I can see that on parsetok.c there is the next block:

```
#ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD
#if 0
static const char with_msg[] =
"%s:%d: Warning: 'with' will become a reserved keyword in Python 2.6\n";

static const char as_msg[] =
"%s:%d: Warning: 'as' will become a reserved keyword in Python 2.6\n";

static void
warn(const char *msg, const char *filename, int lineno)
{
    if (filename == NULL)
        filename = "<string>";
    PySys_WriteStderr(msg, filename, lineno);
}
#endif
#endif
```
I think that the #if 0 block can be remove safely, right?

I don't know if the #ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD we can remove.
History
Date User Action Args
2022-04-11 14:59:23adminsetgithub: 83084
2020-01-13 11:59:17pablogsalsetstatus: open -> closed
resolution: fixed
stage: patch review -> resolved
2019-11-24 00:59:14eamanusetkeywords: + patch
stage: patch review
pull_requests: + pull_request16850
2019-11-24 00:53:25eamanucreate