Message294958
| Author |
Albert-Jan Nijburg |
| Recipients |
Albert-Jan Nijburg, georg.brandl, josephgordon, martin.panter, meador.inge, serhiy.storchaka, vstinner |
| Date |
2017年06月01日.17:20:21 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAO1rg=0=XqS+-3pM4GpWQBp3tXDxpK7dOTL1mN0xMkv3035z+w@mail.gmail.com> |
| In-reply-to |
<1496336925.25.0.685126259038.issue25324@psf.upfronthosting.co.za> |
| Content |
Aah! Oops I can fix later today.
On Thu, 1 Jun 2017 at 18:08, STINNER Victor <report@bugs.python.org> wrote:
>
> STINNER Victor added the comment:
>
> We got a bug report from Coverity:
>
> *** CID 1411801: Incorrect expression (MISSING_COMMA)
> /Parser/tokenizer.c: 111 in ()
> 105 "OP",
> 106 "AWAIT",
> 107 "ASYNC",
> 108 "<ERRORTOKEN>",
> 109 "COMMENT",
> 110 "NL",
> >>> CID 1411801: Incorrect expression (MISSING_COMMA)
> >>> In the initialization of "_PyParser_TokenNames", a suspicious
> concatenated string ""ENCODING<N_TOKENS>"" is produced.
> 111 "ENCODING"
> 112 "<N_TOKENS>"
> 113 };
> 114
> 115
> 116 /* Create and initialize a new tok_state structure */
>
> I missed this typo :-p
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue25324>
> _______________________________________
> |
|