[issue20115] NUL bytes in commented lines

[Armin Rigo]

Armin Rigo added the comment:

PyPy 2.x accepts null characters in all of import, exec and eval, and complains if they occur in non-comment.

PyPy 3.x refuses them in import, which is where this bug report originally comes from (someone complained that CPython 3.x "accepts" them but not PyPy 3.x, even thought this complain doesn't really make sense as CPython just gets very confused by them).  I don't know about exec and eval.

We need a consistent decision for 3.5.  I suppose it's not really worth backporting it to CPython 2.7 - 3.3 - 3.4, but it's your choice.  PyPy will just follow the lead (or keep its current behavior for 2.x if CPython 2.x is not modified).

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue20115>
_______________________________________