Accept PEP 415
This commit is contained in:
parent
5b80ee6d1d
commit
1dfbaf86b4
13
pep-0415.txt
13
pep-0415.txt
|
@ -4,12 +4,13 @@ Version: $Revision$
|
|||
Last-Modified: $Date$
|
||||
Author: Benjamin Peterson <benjamin@python.org>
|
||||
BDFL-Delegate: Nick Coghlan
|
||||
Status: Draft
|
||||
Status: Accepted
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 26-Feb-2012
|
||||
Python-Version: 3.3
|
||||
Post-History: 26-Feb-2012
|
||||
Resolution: http://mail.python.org/pipermail/python-dev/2012-May/119467.html
|
||||
|
||||
|
||||
Abstract
|
||||
|
@ -20,6 +21,13 @@ exception is printed. This is done using the ``raise exc from None``
|
|||
syntax. This PEP proposes to implement context and cause suppression
|
||||
differently.
|
||||
|
||||
|
||||
PEP Acceptance
|
||||
==============
|
||||
|
||||
This PEP was accepted by Nick Coghlan on the 14th of May, 2012.
|
||||
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
||||
|
@ -40,6 +48,7 @@ exceptions, so it's not clear to someone inspecting an exception object why
|
|||
``__cause__`` should be set to ``Ellipsis``. Using ``Ellipsis`` by default for
|
||||
``__cause__`` makes it asymmetrical with ``__context__``.
|
||||
|
||||
|
||||
Proposal
|
||||
========
|
||||
|
||||
|
@ -62,6 +71,7 @@ To summarize, ``raise exc from cause`` will be equivalent to::
|
|||
where ``exc.__cause__ = cause`` implicitly sets
|
||||
``exc.__suppress_context__``.
|
||||
|
||||
|
||||
Patches
|
||||
=======
|
||||
|
||||
|
@ -74,6 +84,7 @@ References
|
|||
.. _issue 14133:
|
||||
http://bugs.python.org/issue14133
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
|
|
14
pep-3144.txt
14
pep-3144.txt
|
@ -5,11 +5,12 @@ Last-Modified: $Date$
|
|||
Author: Peter Moody <pmoody@google.com>
|
||||
BDFL-Delegate: Nick Coghlan
|
||||
Discussions-To: <ipaddr-py-dev@googlegroups.com>
|
||||
Status: Draft
|
||||
Status: Accepted
|
||||
Type: Standards Track
|
||||
Content-Type: text/plain
|
||||
Created: 6-Feb-2012
|
||||
Python-Version: 3.3
|
||||
Resolution: Refer to PEP text
|
||||
|
||||
|
||||
Abstract:
|
||||
|
@ -17,6 +18,11 @@ Abstract:
|
|||
This PEP proposes a design and for an IP address manipulation module for
|
||||
python.
|
||||
|
||||
PEP Acceptance:
|
||||
|
||||
This PEP was accepted by Nick Coghlan (on the BDFL's behalf) on May
|
||||
13th, 2012, based on the PEP text and the reference implementation at
|
||||
|
||||
Motivation:
|
||||
|
||||
Several very good IP address modules for python already exist.
|
||||
|
@ -55,9 +61,9 @@ Background:
|
|||
* A few attributes were renamed to disambiguate their purpose as
|
||||
well. (eg. network, network_address)
|
||||
|
||||
* A number of methods and functions which returned containers in ipaddr now
|
||||
return iterators. This includes, subnets, address_exclude,
|
||||
summarize_address_range and collapse_address_list.
|
||||
* A number of methods and functions which returned containers in ipaddr
|
||||
now return iterators. This includes, subnets, address_exclude,
|
||||
summarize_address_range and collapse_address_list.
|
||||
|
||||
|
||||
Due to the backwards incompatible API changes between ipaddress and ipaddr,
|
||||
|
|
Loading…
Reference in New Issue