On Wed, Apr 18, 2012 at 4:14 PM, Pauli Virtanen wrote:
> Hi,
>
> 18.04.2012 19:57, Alan G Isaac kirjoitti:
>> http://docs.scipy.org/doc/numpy/reference/routines.matlib.html#module-numpy.matlib
>> promises a list of functions that does not appear (at the moment, anyway).
>
> This doesn't seem to be
excellent thank you, that worked perfectly. I just need to remember this
feature next time I need it.
Thanks again
On Thu, Apr 12, 2012 at 11:41 PM, Tim Cera wrote:
> Use 'ma.max' instead of 'np.max'. This might be a bug OR an undocumented
> feature. :-)
>
> import numpy.ma as ma
> mar
12.04.2012 18:43, Ralf Gommers kirjoitti:
[clip]
> My current list of preferences is:
>
> 1. Redmine (if admin overhead is not unreasonable)
> 2. Trac with performance issues solved
> 3. Github
> 4. YouTrack
> 5. Trac with current performance
Redmine seems pretty nice, apparently has all the feat
Hi,
18.04.2012 19:57, Alan G Isaac kirjoitti:
> http://docs.scipy.org/doc/numpy/reference/routines.matlib.html#module-numpy.matlib
> promises a list of functions that does not appear (at the moment, anyway).
This doesn't seem to be due to a technical reason, but rather than
because nobody has wri
Oops, sorry, Keith Goodman kindly pointed out that I had missed out:
On Wed, Apr 18, 2012 at 11:03 AM, Matthew Brett wrote:
> Hi,
>
> I just wanted to point out a situation where the scalar casting rules
> can be a little confusing:
In [110]: a = np.array([-128, 127], dtype=np.int8)
> In [113]:
Hi,
I just wanted to point out a situation where the scalar casting rules
can be a little confusing:
In [113]: a - np.int16(128)
Out[113]: array([-256, -1], dtype=int16)
In [114]: a + np.int16(-128)
Out[114]: array([ 0, -1], dtype=int8)
This is predictable from the nice docs here:
http://doc
http://docs.scipy.org/doc/numpy/reference/routines.matlib.html#module-numpy.matlib
promises a list of functions that does not appear (at the moment, anyway).
Alan Isaac
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/ma
Hi,
1, 2, 3 are integer literals.
1.0, 3.0e2, -42.0 are real (float) literals
'hello world' is a string literal.
As far as I remember, f2py requires a literal variable for the kind.
The solution I have landed on is to write a pure fortran module (using int8, or
whatever), and then wrap this modu
