[Numpy-discussion] 1.6.0b1 half float buffer bug?

Mark Wiebe mwwiebe at gmail.com
Fri Mar 25 14:41:12 EDT 2011

On Fri, Mar 25, 2011 at 11:28 AM, Mark Wiebe <mwwiebe at gmail.com> wrote:

> On Fri, Mar 25, 2011 at 11:14 AM, Eli Stevens (Gmail) <
> wickedgrey at gmail.com> wrote:
>> On Fri, Mar 25, 2011 at 10:35 AM, Mark Wiebe <mwwiebe at gmail.com> wrote:
>> > That said, I think starting a discussion with the Python core developers
>> > about the float16 type is worthwhile. There might be interest in
>> supporting
>> > the float16 type in the struct interface, something that would be
>> required
>> > as part of amending PEP 3118.
>> That's something that wouldn't see production until Python 3.3, right?
>>  I'm imagining that the buffer spec in use wouldn't change during the
>> 2.7.x series, unless it's unusually accepting of changes.
> That's true, but explaining the hoops being jumped through to support a new
> data type across multiple Python plugins could help evolve the spec if
> necessary, and they may have some good suggestions.

Thinking about that a bit more, maybe a convention added to PEP 3118 for
custom types would be useful. For float16, labeling it as 'H' makes sense,
then it could be followed by metadata identifying the custom type, like

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20110325/8d66b1f0/attachment.html>

More information about the NumPy-Discussion mailing list