From 0334c3c735a3616c5016b8013796ca08307f88de Mon Sep 17 00:00:00 2001 From: Berker Peksag Date: Sun, 21 Feb 2016 22:00:12 +0200 Subject: [PATCH] Issue #26401: Fix compile() documentation After 25032ec29315, compile() will raise a ValueError if source contains null bytes. Patch by SilentGhost. --- Doc/library/functions.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Doc/library/functions.rst b/Doc/library/functions.rst index 6e98cfb945..65f53dd193 100644 --- a/Doc/library/functions.rst +++ b/Doc/library/functions.rst @@ -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]]) -- 2.40.0