[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] The future of Numeric



If we're phasing out Numeric, wouldn't it be a good idea to make NumPy
the default when both are available?
-FM

On Tue, Dec 16, 2008 at 8:39 PM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
> Yes, NumPy is nicer. Numeric is showing its age. NumPy makes better use of
> the Python features introduced with Python 2.2, unified types and classes.
> As I mentioned though, Numeric support won't disappear from Pygame just yet.
> Rather any future efforts will be concentrated on NumPy.
>
> Lenard
>
> René Dudfield wrote:
>>
>> hi,
>>
>> yeah Numpy is the much newer version of Numeric, and is compatible in
>> many ways.  There's also a document around somewhere that tells you
>> what methods to use for Numeric ones where they are not compatible.
>>
>> It's nicer in many regards, and Numeric has been marked obsolete a few
>> years ago.
>>
>> So definitely update any code you can to numpy :)
>>
>>
>> cheers,
>>
>> On Wed, Dec 17, 2008 at 10:08 AM, Ian Mallett <geometrian@xxxxxxxxx>
>> wrote:
>>
>>>
>>> I'm not really familiar with either.  When I ported the .obj file loader
>>> to
>>> use vertex arrays (and in the future VBOs), I needed to add a vertex
>>> attribute array, which wanted a pointer (in C).  In Python, the function
>>> was
>>> placated with array.tostring().  That was using Numeric--does NumPy have
>>> the
>>> same thing?
>>> Ian
>>>
>
>
> --
> Lenard Lindstrom
> <len-l@xxxxxxxxx>
>
>