Mark PEP 399 as final. Along the way update the post history and fix a
very nit-picky detail that Benjamin pointed out.
This commit is contained in:
parent
605d5638fe
commit
d46cbd81f8
|
@ -3,12 +3,12 @@ Title: Pure Python/C Accelerator Module Compatibility Requirements
|
|||
Version: $Revision: 88219 $
|
||||
Last-Modified: $Date: 2011-01-27 13:47:00 -0800 (Thu, 27 Jan 2011) $
|
||||
Author: Brett Cannon <brett@python.org>
|
||||
Status: Draft
|
||||
Status: Final
|
||||
Type: Informational
|
||||
Content-Type: text/x-rst
|
||||
Created: 04-Apr-2011
|
||||
Python-Version: 3.3
|
||||
Post-History: 04-Apr-2011, 12-Apr-2011, 17-Jul-2011
|
||||
Post-History: 04-Apr-2011, 12-Apr-2011, 17-Jul-2011, 15-Aug-2011
|
||||
|
||||
Abstract
|
||||
========
|
||||
|
@ -176,8 +176,8 @@ objects to prevent accidental dependence on specific types. For
|
|||
instance, if a function accepts a sequence then the C code should
|
||||
default to using `PyObject_GetItem()` instead of something like
|
||||
`PyList_GetItem()`. C code is allowed to have a fast path if the
|
||||
proper `PyList_Check()` is used, but otherwise APIs should work with
|
||||
any object that duck types to the proper interface instead of a
|
||||
proper `PyList_CheckExact()` is used, but otherwise APIs should work
|
||||
with any object that duck types to the proper interface instead of a
|
||||
specific type.
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue