iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 578: Mark as Final (#3811)

This commit is contained in:
Hugo van Kemenade 2024-06-03 08:51:21 -06:00 committed by GitHub
parent 097f2d8885
commit e3fae76486
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
peps/pep-0578.rst
View File

@ -1,16 +1,15 @@
PEP: 578
Title: Python Runtime Audit Hooks
Version: $Revision$
Last-Modified: $Date$
Author: Steve Dower <steve.dower@python.org>
BDFL-Delegate: Christian Heimes <christian@python.org>
Status: Accepted
Status: Final
Type: Standards Track
Content-Type: text/x-rst
Created: 16-Jun-2018
Python-Version: 3.8
Post-History: 28-Mar-2019, 07-May-2019
.. canonical-doc:: :ref:`python:audit-events`
Abstract
========
@ -85,7 +84,7 @@ The aim of these changes is to enable both application developers and
system administrators to integrate Python into their existing
monitoring systems without dictating how those systems look or behave.
We propose two API changes to enable this: an Audit Hook and Verified
We propose two API changes to enable this: an Audit Hook and Verified
Open Hook. Both are available from Python and native code, allowing
applications and frameworks written in pure Python code to take
advantage of the extra messages, while also allowing embedders or
@ -284,7 +283,7 @@ API Availability
While all the functions added here are considered public and stable API,
the behavior of the functions is implementation specific. Most
descriptions here refer to the CPython implementation, and while other
descriptions here refer to the CPython implementation, and while other
implementations should provide the functions, there is no requirement
that they behave the same.
@ -506,7 +505,7 @@ The argument that this is "security by obscurity" is valid, but
irrelevant. Security by obscurity is only an issue when there are no
other protective mechanisms; obscurity as the first step in avoiding
attack is strongly recommended (see `this article
<https://danielmiessler.com/study/security-by-obscurity/>`_ for
<https://danielmiessler.com/p/security-by-obscurity/>`_ for
discussion).
This idea is rejected because there are no appropriate reasons for an
@ -557,7 +556,7 @@ a secure or audited environment.
References
==========
.. [1] Python Performance Benchmark Suite `<https://github.com/python/performance>`_
.. [1] Python Performance Benchmark Suite `<https://github.com/python/pyperformance>`_
.. [2] Python Security model - Sandbox `<https://python-security.readthedocs.io/security.html#sandbox>`_
@ -567,4 +566,4 @@ Copyright
Copyright (c) 2019 by Microsoft Corporation. This material may be
distributed only subject to the terms and conditions set forth in the
Open Publication License, v1.0 or later (the latest version is presently
available at http://www.opencontent.org/openpub/).
available at https://spdx.org/licenses/OPUBL-1.0.html).