PEP 522: Note upstream rejection

This commit is contained in:
Nick Coghlan 2016-08-08 12:48:31 +10:00
parent 0596b09948
commit fc085af9c1
1 changed files with 15 additions and 1 deletions

View File

@ -3,12 +3,13 @@ Title: Allow BlockingIOError in security sensitive APIs
Version: $Revision$ Version: $Revision$
Last-Modified: $Date$ Last-Modified: $Date$
Author: Nick Coghlan <ncoghlan@gmail.com>, Nathaniel J. Smith <njs@pobox.com> Author: Nick Coghlan <ncoghlan@gmail.com>, Nathaniel J. Smith <njs@pobox.com>
Status: Draft Status: Rejected
Type: Standards Track Type: Standards Track
Content-Type: text/x-rst Content-Type: text/x-rst
Requires: 506 Requires: 506
Created: 16 June 2016 Created: 16 June 2016
Python-Version: 3.6 Python-Version: 3.6
Resolution: https://mail.python.org/pipermail/security-sig/2016-August/000101.html
Abstract 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 generator, or Linux VMs that aren't configured to accept entropy from the
VM host) VM host)
Relationship with other PEPs 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. ``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 Changes independent of this PEP
=============================== ===============================