Fernando Perez wrote:

O'Keefe, Michael wrote:

...

...

Now, the data-type object itself is the preferred way. I need to figure out what to do with these functions now and see if they even have any use anymore.

Thanks Travis.

With regard to what to do with the functions, I only ended up trying them because they were there. From my point of view, I'd love to learn how to code the "right" way. To that end, any means of informing the user of "deprecated" functions (or just taking them out) would be fine with me. However, I realize some may have legacy code and so I would defer to their opinions.

Python has a proper framework for deprecation warnings. I'd say we use that, and Travis can ruthlessly deprecate anything that's just compatibility noise.

Perhaps 1.0 can keep old but deprecated things around (numpy will see a LOT of use once 1.0 comes out, far more than the current svn testing crowd). Then, as of 1.1 or 1.2 or whatever, those can be removed.

Cheers,

f

One of the deprecated names is ArrayType. This seems to be closer to the Python style than ndarray. Colin W.

Travis Oliphant wrote:

Colin J. Williams wrote:

...

One of the deprecated names is ArrayType. This seems to be closer to the Python style than ndarray.

Not really. I agree with what you say below, but doesn't ArrayType have a greater similarity to the Python types than ndarray?

[Dbg]>>> import types [Dbg]>>> dir(types) ['BooleanType', 'BufferType', 'BuiltinFunctionType', 'BuiltinMethodType', 'ClassType', 'CodeType', 'ComplexType', 'DictProxyType', 'DictType', 'DictionaryType', 'EllipsisType', 'FileType', 'FloatType', 'FrameType', 'FunctionType', 'GeneratorType', 'Instance Type', 'IntType', 'LambdaType', 'ListType', 'LongType', 'MethodType', 'ModuleType', 'NoneType', 'NotImplementedType', 'ObjectType', 'SliceType', 'StringType', 'StringTypes', 'TracebackType', 'TupleType', 'TypeType', 'UnboundMethodType', 'UnicodeType', 'XRan geType', '__builtins__', '__doc__', '__file__', '__name__'] [Dbg]>>> I presume that the aim is still that numpy will become a part of the Python offering. Colin W.

Rather than test: type(var) == types.IntType you should be testing isinstance(var, int)

just like rather than testing type(somearray) == ArrayType

you should be testing isinstance(somearray, ndarray)

Python style has changed a bit since 2.2 allowed sub-typing builtings

-Travis

Gerard Vermeulen wrote:

On Wed, 01 Feb 2006 11:15:09 -0500 "Colin J. Williams" wrote:

[ depration + style ]

...

[Dbg]>>> import types [Dbg]>>> dir(types) ['BooleanType', 'BufferType', 'BuiltinFunctionType', 'BuiltinMethodType', 'ClassType', 'CodeType', 'ComplexType', 'DictProxyType', 'DictType', 'DictionaryType', 'EllipsisType', 'FileType', 'FloatType', 'FrameType', 'FunctionType', 'GeneratorType', 'Instance Type', 'IntType', 'LambdaType', 'ListType', 'LongType', 'MethodType', 'ModuleType', 'NoneType', 'NotImplementedType', 'ObjectType', 'SliceType', 'StringType', 'StringTypes', 'TracebackType', 'TupleType', 'TypeType', 'UnboundMethodType', 'UnicodeType', 'XRan geType', '__builtins__', '__doc__', '__file__', '__name__'] [Dbg]>>>

Isn't the types module becoming superfluous?

That's the point I was trying to make. ArrayType is to ndarray as DictionaryType is to dict. My understanding is that the use of types.DictionaryType is discouraged. -Travis