Skip to content

Commit e3fae76

Browse files
authored
PEP 578: Mark as Final (#3811)
1 parent 097f2d8 commit e3fae76

1 file changed

Lines changed: 8 additions & 9 deletions

File tree

peps/pep-0578.rst

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,15 @@
11
PEP: 578
22
Title: Python Runtime Audit Hooks
3-
Version: $Revision$
4-
Last-Modified: $Date$
53
Author: Steve Dower <steve.dower@python.org>
64
BDFL-Delegate: Christian Heimes <christian@python.org>
7-
Status: Accepted
5+
Status: Final
86
Type: Standards Track
9-
Content-Type: text/x-rst
107
Created: 16-Jun-2018
118
Python-Version: 3.8
129
Post-History: 28-Mar-2019, 07-May-2019
1310

11+
.. canonical-doc:: :ref:`python:audit-events`
12+
1413
Abstract
1514
========
1615

@@ -85,7 +84,7 @@ The aim of these changes is to enable both application developers and
8584
system administrators to integrate Python into their existing
8685
monitoring systems without dictating how those systems look or behave.
8786

88-
We propose two API changes to enable this: an Audit Hook and Verified
87+
We propose two API changes to enable this: an Audit Hook and Verified
8988
Open Hook. Both are available from Python and native code, allowing
9089
applications and frameworks written in pure Python code to take
9190
advantage of the extra messages, while also allowing embedders or
@@ -284,7 +283,7 @@ API Availability
284283

285284
While all the functions added here are considered public and stable API,
286285
the behavior of the functions is implementation specific. Most
287-
descriptions here refer to the CPython implementation, and while other
286+
descriptions here refer to the CPython implementation, and while other
288287
implementations should provide the functions, there is no requirement
289288
that they behave the same.
290289

@@ -506,7 +505,7 @@ The argument that this is "security by obscurity" is valid, but
506505
irrelevant. Security by obscurity is only an issue when there are no
507506
other protective mechanisms; obscurity as the first step in avoiding
508507
attack is strongly recommended (see `this article
509-
<https://danielmiessler.com/study/security-by-obscurity/>`_ for
508+
<https://danielmiessler.com/p/security-by-obscurity/>`_ for
510509
discussion).
511510

512511
This idea is rejected because there are no appropriate reasons for an
@@ -557,7 +556,7 @@ a secure or audited environment.
557556
References
558557
==========
559558

560-
.. [1] Python Performance Benchmark Suite `<https://github.com/python/performance>`_
559+
.. [1] Python Performance Benchmark Suite `<https://github.com/python/pyperformance>`_
561560
562561
.. [2] Python Security model - Sandbox `<https://python-security.readthedocs.io/security.html#sandbox>`_
563562
@@ -567,4 +566,4 @@ Copyright
567566
Copyright (c) 2019 by Microsoft Corporation. This material may be
568567
distributed only subject to the terms and conditions set forth in the
569568
Open Publication License, v1.0 or later (the latest version is presently
570-
available at http://www.opencontent.org/openpub/).
569+
available at https://spdx.org/licenses/OPUBL-1.0.html).

0 commit comments

Comments
 (0)