[issue38903] #if 0 block on parsetok.c

[Pablo Galindo Salgado]

Change by Pablo Galindo Salgado :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38903] #if 0 block on parsetok.c

[Emmanuel Arias]

Change by Emmanuel Arias :


--
keywords: +patch
pull_requests: +16850
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/17365

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue38903] #if 0 block on parsetok.c

[Emmanuel Arias]

New submission from Emmanuel Arias :

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 = "";
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.

--
messages: 357387
nosy: eamanu
priority: normal
severity: normal
status: open
title: #if 0 block on parsetok.c
versions: Python 3.9

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com