Merge #20145 backport: delete whatsnew entry.

diff --cc Doc/whatsnew/3.5.rst
index 2447898f88f35a55491eaaa6ac18913f5b6627ee,0000000000000000000000000000000000000000..b18bcd2d79ddb9da4fa15131410037166e2e3463
mode 100644,000000..100644
--- 1/Doc/whatsnew/3.5.rst
--- /dev/null
+++ b/Doc/whatsnew/3.5.rst
@@@ -1,200 -1,0 +1,194 @@@
- 
- * :meth:`unittest.TestCase.assertRaisesRegex` and
-   :meth:`~unittest.TestCase.assertWarnsRegex` now raise a :exc:`TypeError` if
-   the second argument is not a string or a compiled :mod:`regex`.  You may have
-   tests with an invalid second argument that have until 3.5 been falsely
-   passing which will now raise TypeErrors (:issue:`20145`).
 +****************************
 +  What's New In Python 3.5
 +****************************
 +
 +:Release: |release|
 +:Date: |today|
 +
 +.. Rules for maintenance:
 +
 +   * Anyone can add text to this document.  Do not spend very much time
 +   on the wording of your changes, because your text will probably
 +   get rewritten to some degree.
 +
 +   * The maintainer will go through Misc/NEWS periodically and add
 +   changes; it's therefore more important to add your changes to
 +   Misc/NEWS than to this file.
 +
 +   * This is not a complete list of every single change; completeness
 +   is the purpose of Misc/NEWS.  Some changes I consider too small
 +   or esoteric to include.  If such a change is added to the text,
 +   I'll just remove it.  (This is another reason you shouldn't spend
 +   too much time on writing your addition.)
 +
 +   * If you want to draw your new text to the attention of the
 +   maintainer, add 'XXX' to the beginning of the paragraph or
 +   section.
 +
 +   * It's OK to just add a fragmentary note about a change.  For
 +   example: "XXX Describe the transmogrify() function added to the
 +   socket module."  The maintainer will research the change and
 +   write the necessary text.
 +
 +   * You can comment out your additions if you like, but it's not
 +   necessary (especially when a final release is some months away).
 +
 +   * Credit the author of a patch or bugfix.   Just the name is
 +   sufficient; the e-mail address isn't necessary.
 +
 +   * It's helpful to add the bug/patch number as a comment:
 +
 +   XXX Describe the transmogrify() function added to the socket
 +   module.
 +   (Contributed by P.Y. Developer in :issue:`12345`.)
 +
 +   This saves the maintainer the effort of going through the Mercurial log
 +   when researching a change.
 +
 +This article explains the new features in Python 3.5, compared to 3.4.
 +
 +For full details, see the :source:`Misc/NEWS` file.
 +
 +.. note:: Prerelease users should be aware that this document is currently in
 +   draft form. It will be updated substantially as Python 3.5 moves towards
 +   release, so it's worth checking back even after reading earlier versions.
 +
 +
 +.. seealso::
 +
 +    .. :pep:`4XX` - Python 3.5 Release Schedule
 +
 +
 +Summary -- Release highlights
 +=============================
 +
 +.. This section singles out the most important changes in Python 3.3.
 +   Brevity is key.
 +
 +New syntax features:
 +
 +* None yet.
 +
 +New library modules:
 +
 +* None yet.
 +
 +New built-in features:
 +
 +* None yet.
 +
 +Implementation improvements:
 +
 +* When the ``LC_TYPE`` locale is the POSIX locale (``C`` locale),
 +  :py:data:`sys.stdin` and :py:data:`sys.stdout` are now using the
 +  ``surrogateescape`` error handler, instead of the ``strict`` error handler
 +  (:issue:`19977`).
 +
 +Significantly Improved Library Modules:
 +
 +* None yet.
 +
 +Security improvements:
 +
 +* None yet.
 +
 +Please read on for a comprehensive list of user-facing changes.
 +
 +
 +.. PEP-sized items next.
 +
 +.. _pep-4XX:
 +
 +.. PEP 4XX: Virtual Environments
 +.. =============================
 +
 +
 +.. (Implemented by Foo Bar.)
 +
 +.. .. seealso::
 +
 +    :pep:`4XX` - Python Virtual Environments
 +       PEP written by Carl Meyer
 +
 +
 +
 +
 +Other Language Changes
 +======================
 +
 +Some smaller changes made to the core Python language are:
 +
 +* None yet.
 +
 +
 +
 +New Modules
 +===========
 +
 +.. module name
 +.. -----------
 +
 +* None yet.
 +
 +
 +Improved Modules
 +================
 +
 +* :class:`xmlrpc.client.ServerProxy` is now a :term:`context manager`
 +  (contributed by Claudiu Popa in :issue:`20627`).
 +
 +
 +Optimizations
 +=============
 +
 +Major performance enhancements have been added:
 +
 +* None yet.
 +
 +
 +Build and C API Changes
 +=======================
 +
 +Changes to Python's build process and to the C API include:
 +
 +* None yet.
 +
 +
 +Deprecated
 +==========
 +
 +Unsupported Operating Systems
 +-----------------------------
 +
 +* None yet.
 +
 +
 +Deprecated Python modules, functions and methods
 +------------------------------------------------
 +
 +* The :mod:`formatter` module has now graduated to full deprecation and is still
 +  slated for removal in Python 3.6.
 +
 +
 +Deprecated functions and types of the C API
 +-------------------------------------------
 +
 +* None yet.
 +
 +
 +Deprecated features
 +-------------------
 +
 +* None yet.
 +
 +
 +Porting to Python 3.5
 +=====================
 +
 +This section lists previously described changes and other bugfixes
 +that may require changes to your code.
 +
 +* Before Python 3.5, a :class:`datetime.time` object was considered to be false
 +  if it represented midnight in UTC.  This behavior was considered obscure and
 +  error-prone and has been removed in Python 3.5.  See :issue:`13936` for full
 +  details.