diff options
author | 2014-02-27 18:32:32 -0500 | |
---|---|---|
committer | 2014-02-27 18:32:32 -0500 | |
commit | ecef6cd2f1de88980dfbf417191a7b7f095ac5f2 (patch) | |
tree | 609f95530eaed643e84e6dc60a0dae5fdac88324 | |
parent | merge 3.3 (diff) | |
download | cpython-ecef6cd2f1de88980dfbf417191a7b7f095ac5f2.tar.gz cpython-ecef6cd2f1de88980dfbf417191a7b7f095ac5f2.tar.bz2 cpython-ecef6cd2f1de88980dfbf417191a7b7f095ac5f2.zip |
whatsnew: return types of re functions.
-rw-r--r-- | Doc/whatsnew/3.4.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst index 16799ff70c8..562a29a345f 100644 --- a/Doc/whatsnew/3.4.rst +++ b/Doc/whatsnew/3.4.rst @@ -1987,6 +1987,13 @@ Changes in the Python API in theory this should not cause backward compatibility issues since the disallowed command forms didn't make any sense and are unlikely to be in use. +* The :func:`re.split`, :func:`re.findall`, and :func:`re.sub` functions, and + the :meth:`~re.match.group` and :meth:`~re.match.groups` methods of + :class:``match`` objects now always return a *bytes* object when the string + to be matched is a :term:`bytes-like object`. Previously the return type + matched the input type, so if your code was depending on the return value + being, say, a ``bytearray``, you will need to change your code. + Changes in the C API -------------------- |