Withdraw PEP 504 in favour of 506
This commit is contained in:
parent
56ef8a5943
commit
1b6ff2b4f6
17
pep-0504.txt
17
pep-0504.txt
|
@ -3,7 +3,7 @@ Title: Using the System RNG by default
|
||||||
Version: $Revision$
|
Version: $Revision$
|
||||||
Last-Modified: $Date$
|
Last-Modified: $Date$
|
||||||
Author: Nick Coghlan <ncoghlan@gmail.com>
|
Author: Nick Coghlan <ncoghlan@gmail.com>
|
||||||
Status: Draft
|
Status: Withdrawn
|
||||||
Type: Standards Track
|
Type: Standards Track
|
||||||
Content-Type: text/x-rst
|
Content-Type: text/x-rst
|
||||||
Created: 15-Sep-2015
|
Created: 15-Sep-2015
|
||||||
|
@ -38,6 +38,21 @@ deterministic random number generator process wide either by using a new
|
||||||
To minimise the impact on existing code, module level APIs that require
|
To minimise the impact on existing code, module level APIs that require
|
||||||
determinism will implicitly switch to the deterministic PRNG.
|
determinism will implicitly switch to the deterministic PRNG.
|
||||||
|
|
||||||
|
PEP Withdrawal
|
||||||
|
==============
|
||||||
|
|
||||||
|
During discussion of this PEP, Steven D'Aprano proposed the simpler alternative
|
||||||
|
of offering a standardised ``secrets`` module that provides "one obvious way"
|
||||||
|
to handle security sensitive tasks like generating default passwords and other
|
||||||
|
tokens.
|
||||||
|
|
||||||
|
Steven's proposal has the desired effect of aligning the easy way to generate
|
||||||
|
such tokens and the right way to generate them, without introducing any
|
||||||
|
compatibility risks for the existing ``random`` module API, so this PEP has
|
||||||
|
been deferred in favour of further work on refining Steven's proposal as
|
||||||
|
PEP 506.
|
||||||
|
|
||||||
|
|
||||||
Proposal
|
Proposal
|
||||||
========
|
========
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue