I'm not subscribed to the main Python list, so I'll just ask here.
It looks like the protocol doesn't support any floating point image formats,
judging from the big table of formats in the PEP. These are becoming more
important these days in computer graphics as a way to pass around high
dynamic
[Sorry for the cross-posting, but I think this may be relevant for
both NumPy and ndimage.]
Hello everyone,
I have submitted to the Python core developers a new PEP (Python
Enhancement Proposal):
http://www.python.org/dev/peps/pep-0368/
It proposes two things:
* the creation of a standard
El dt 03 de 07 del 2007 a les 10:34 +0200, en/na Sebastian Haase va
escriure:
> Thanks for the reply.
> Rethinking the question ... wasn't there an attribute named something like:
> is_native()
> ??
In [3]:a.dtype.isnative
Out[3]:True
:)
--
Francesc Altet| Be careful about using the follow
Thanks for the reply.
Rethinking the question ... wasn't there an attribute named something like:
is_native()
??
The a.dtype.str[0] is certainly better than nothing ... just doesn't
look very good ;-)
-Sebastian
On 7/3/07, Francesc Altet <[EMAIL PROTECTED]> wrote:
> El dt 03 de 07 del 2007 a
El dt 03 de 07 del 2007 a les 08:35 +0200, en/na Sebastian Haase va
escriure:
> any comments !?
>
> On 6/25/07, Sebastian Haase <[EMAIL PROTECTED]> wrote:
> > Hi,
> > Suppose I'm on a little-edian system.
> > Could I have a little-endian numpy array arr, where
> > arr.dtype.byteorder
> > would act
