From: R David Murray <rdmurray@bitdance.com>
Date: Tue, 11 Feb 2014 00:12:52 +0000 (-0500)
Subject: whatsnew: bytes/bytearray.join args, PYTHONPATH= is same as not set.
X-Git-Tag: v3.4.1rc1~233^2~365
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=96eeddba0542f0b5323659ffb0fa7038032899d8;p=thirdparty%2FPython%2Fcpython.git

whatsnew: bytes/bytearray.join args, PYTHONPATH= is same as not set.
---

diff --git a/Doc/whatsnew/3.4.rst b/Doc/whatsnew/3.4.rst
index dcd9284095f8..ed6987645988 100644
--- a/Doc/whatsnew/3.4.rst
+++ b/Doc/whatsnew/3.4.rst
@@ -364,6 +364,9 @@ Some smaller changes made to the core Python language are:
   Contributed by Victor Stinner, Kang-Hao (Kenny) Lu and Serhiy Storchaka in
   :issue:`12892`.
 
+* :class:`bytes`.join() and :class:`bytearray`.join() now accept arbitrary
+  buffer objects as arguments.  (Contributed by Antoine Pitrou in
+  :issue:`15958`.)
 
 
 New Modules
@@ -1609,6 +1612,20 @@ Porting to Python 3.4
 This section lists previously described changes and other bugfixes
 that may require changes to your code.
 
+
+Changes in 'python' command behavior
+------------------------------------
+
+* In a posix shell, setting an environment variable to an empty value is
+  generally equivalent to not setting it at all.  In particular, this is true
+  for the :envvar:`PATH` environment variable.  However, setting
+  :envvar:`PYTHONPATH` to an empty value was *not* equivalent to not setting it
+  at all: setting :envvar:`PYTHONPATH` to an empty value was equivalent to
+  setting it to ``.``, which leads to confusion when reasoning by analogy to
+  how :envvar:`PATH` works.  The behavior now conforms to the normal posix
+  convention.
+
+
 Changes in the Python API
 -------------------------