PEP: unassigned
Title: Revising the buffer protocol
Version: $Revision: $
Last-Modified: $Date: $
Author: Travis Oliphant [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Created: 28-Aug-2006
Python-Version: 3000
Abstract
This PEP proposes re-designing the buffer API (PyBufferProcs
On 2/27/07, Travis Oliphant [EMAIL PROTECTED] wrote:
PEP: unassigned
Title: Revising the buffer protocol
Version: $Revision: $
Last-Modified: $Date: $
Author: Travis Oliphant [EMAIL PROTECTED]
Status: Draft
Type: Standards Track
Created: 28-Aug-2006
Python-Version: 3000
snip
Additions to
Charles R Harris wrote:
On 2/27/07, *Travis Oliphant* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
PEP: unassigned
Title: Revising the buffer protocol
Version: $Revision: $
Last-Modified: $Date: $
Author: Travis Oliphant [EMAIL PROTECTED]
mailto:[EMAIL
On 27/02/07, Travis Oliphant [EMAIL PROTECTED] wrote:
The problem is that we aren't really specifying floating-point
standards, we are specifying float, double and long double as whatever
the compiler understands.
There are some platforms which don't follow the IEEE 754 standard.
This
Charles R Harris wrote:
The problem is that we aren't really specifying floating-point
standards, we are specifying float, double and long double as whatever
the compiler understands.
There are some platforms which don't follow the IEEE 754 standard.
This format
On 2/27/07, Travis Oliphant [EMAIL PROTECTED] wrote:
Charles R Harris wrote:
The problem is that we aren't really specifying floating-point
standards, we are specifying float, double and long double as
whatever
the compiler understands.
There are some platforms which
