From ecef6cd2f1de88980dfbf417191a7b7f095ac5f2 Mon Sep 17 00:00:00 2001
From: R David Murray <rdmurray@bitdance.com>
Date: Thu, 27 Feb 2014 18:32:32 -0500
Subject: [PATCH] whatsnew: return types of re functions.

---
 Doc/whatsnew/3.4.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
index 16799ff70c..562a29a345 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
 --------------------
-- 
2.40.0