➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paulehoffman
Recipients Eli.Stevens, asvetlov, belopolsky, mark.dickinson, mark.wiebe, paulehoffman, pitrou
Date 2013-04-23.17:41:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1366738885.29.0.396671311163.issue11734@psf.upfronthosting.co.za>
In-reply-to
Content 
I *think* what you are saying is that there will be no float16 type, but the result of struct.unpack('eorwhatever', packed_stuff)[0] will be the same as struct.unpack('f', packed_stuff)[0], yes? If so, that's what I wanted. I don't want a new float16; I want the output of unpacking a half-precision to be the same as unpacking the other two.

I didn't see a statement like that earlier in the thread, but I could have missed it. Or maybe this was covered in msg132976?
History
Date User Action Args
2013-04-23 17:41:25paulehoffmansetrecipients: + paulehoffman, mark.dickinson, belopolsky, pitrou, asvetlov, Eli.Stevens, mark.wiebe
2013-04-23 17:41:25paulehoffmansetmessageid: <1366738885.29.0.396671311163.issue11734@psf.upfronthosting.co.za>
2013-04-23 17:41:25paulehoffmanlinkissue11734 messages
2013-04-23 17:41:25paulehoffmancreate