Issue #26401: Fix compile() documentation

After 25032ec29315, compile() will raise a ValueError
if source contains null bytes.

Patch by SilentGhost.
This commit is contained in:
Berker Peksag 2016-02-21 22:00:12 +02:00
parent 31feb71f80
commit 0334c3c735
1 changed files with 5 additions and 1 deletions

View File

@ -230,7 +230,7 @@ are always available. They are listed here in alphabetical order.
or ``2`` (docstrings are removed too).
This function raises :exc:`SyntaxError` if the compiled source is invalid,
and :exc:`TypeError` if the source contains null bytes.
and :exc:`ValueError` if the source contains null bytes.
If you want to parse Python code into its AST representation, see
:func:`ast.parse`.
@ -246,6 +246,10 @@ are always available. They are listed here in alphabetical order.
Allowed use of Windows and Mac newlines. Also input in ``'exec'`` mode
does not have to end in a newline anymore. Added the *optimize* parameter.
.. versionchanged:: 3.5
Previously, :exc:`TypeError` was raised when null bytes were encountered
in *source*.
.. class:: complex([real[, imag]])