This is slightly off-topic, but probably of interest to anyone reading
this thread:
Is there any reason why we don't use --fcompiler=gfortran as an alias
for --fcompiler=gfortran (and --fcompiler=g77 as an alias for
--fcompiler=gnu, for that matter)?
Those seem to me to be much more mnemonic n
I wrote:
> This is slightly off-topic, but probably of interest to anyone reading
> this thread:
>
> Is there any reason why we don't use --fcompiler=gfortran as an alias
> for --fcompiler=gfortran (and --fcompiler=g77 as an alias for
> --fcompiler=gnu, for that matter)?
But, sorry, of course
Just realized this might be important I'm using Python2.5.1
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
I have the potential to add OS X Server Intel (64-bit) and OS X Intel
(32-bit) to the list, if I can convince my boss that the security risk
(including DOS from compile times) is minimal. I've compiled both
numpy and scipy many times, so I'm not worried about resources for a
single compile/test, bu
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 actually be "<"
> instead of "=" !?
>
> There are two kinds of systems: little edian and big end
