PEP 522: Note upstream rejection

pep-0522.txt

@@ -3,12 +3,13 @@ Title: Allow BlockingIOError in security sensitive APIs
 Version: $Revision$
 Last-Modified: $Date$
 Author: Nick Coghlan <ncoghlan@gmail.com>, Nathaniel J. Smith <njs@pobox.com>
-Status: Draft
+Status: Rejected
 Type: Standards Track
 Content-Type: text/x-rst
 Requires: 506
 Created: 16 June 2016
 Python-Version: 3.6
+Resolution: https://mail.python.org/pipermail/security-sig/2016-August/000101.html
 
 
 Abstract
@@ -55,6 +56,7 @@ potentially be encountered in the following situations:
   generator, or Linux VMs that aren't configured to accept entropy from the
   VM host)
 
+
 Relationship with other PEPs
 ============================
 
@@ -64,6 +66,18 @@ This PEP competes with Victor Stinner's PEP 524, which proposes to make
 ``os.urandom`` itself implicitly block when the system RNG is not ready.
 
 
+PEP Rejection
+=============
+
+For the reference implementation, Guido rejected this PEP in favour of the
+unconditional implicit blocking proposal in PEP 524.
+
+This means any further discussion of appropriate default behaviour for
+``os.urandom()`` in system Python installations in Linux distributions should
+take place on the respective distro mailing lists, rather than on the upstream
+CPython mailing lists.
+
+
 Changes independent of this PEP
 ===============================