On 9 Apr 2015, at 9:41 pm, Andrew Collette wrote:
>
>> Congrats! Also btw, you might want to switch to a new subject line format
>> for these emails -- the mention of Python 2.5 getting hdf5 support made me
>> do a serious double take before I figured out what was going on, and 2.6 and
>> 2.7 wil
> Congrats! Also btw, you might want to switch to a new subject line format
> for these emails -- the mention of Python 2.5 getting hdf5 support made me
> do a serious double take before I figured out what was going on, and 2.6 and
> 2.7 will be even worse :-)
Ha! Didn't even think of that. For
On Apr 9, 2015 2:41 PM, "Nathaniel Smith" wrote:
>
> (Off-list)
Doh, we do reply-to munging, don't we. Oh well.
-n
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Thu, Apr 9, 2015 at 2:41 PM, Nathaniel Smith wrote:
> (Off-list)
>
> Congrats! Also btw, you might want to switch to a new subject line format
> for these emails -- the mention of Python 2.5 getting hdf5 support made me
> do a serious double take before I figured out what was going on, and 2.6
(Off-list)
Congrats! Also btw, you might want to switch to a new subject line format
for these emails -- the mention of Python 2.5 getting hdf5 support made me
do a serious double take before I figured out what was going on, and 2.6
and 2.7 will be even worse :-)
On Apr 9, 2015 2:07 PM, "Andrew Co
Announcing HDF5 for Python (h5py) 2.5.0
The h5py team is happy to announce the availability of h5py 2.5.0.
This release introduces experimental support for the highly-anticipated
"Single Writer Multiple Reader" (SWMR) feature in the upcoming HDF5 1.10
rele
On Thu, Apr 9, 2015 at 10:11 AM, Alan G Isaac wrote:
> > Alan wrote:
>>> 3. I admit, my students are NOT using non-boolen fancy indexing on
>>> >multidimensional arrays. (As far as I know.) Are yours?
The only confusing case is mixing slices and integer array indexing
for ndim > 2. The rest loo
> Alan wrote:
>> 3. I admit, my students are NOT using non-boolen fancy indexing on
>> >multidimensional arrays. (As far as I know.) Are yours?
On 4/9/2015 2:22 AM, Nathaniel Smith wrote:
> Well, okay, this would explain it, since integer fancy indexing is
> exactly the confusing case:-) On th
On 4/9/2015 1:57 AM, Nathaniel Smith wrote:
> Do you think there's anything we could be
> doing to reduce this kind of adrenaline reaction while still allowing
> for relaxed discussion about out-there ideas?
numpy3...@scipy.org
:-)
___
NumPy-Discussion
Hello list,
I want to send somebody my compiled fortran extension on a Mac (compiled
with f2py and gfortran).
Problem is that it doesn't work on other Macs unless they also instal xcode
(2 GB, yikes!) and gfortran. So apparently there are some additional files
missing when I just send the compile
On Thu, Apr 9, 2015 at 8:07 AM, Sebastian Berg
wrote:
>
> On Do, 2015-04-09 at 08:50 +0200, Sebastian Berg wrote:
> > 3. I do not know if it possible or useful, but I could imagine a module
> > wide switch (similar to __future__ imports) to change the default
> > indexing behaviour.
>
> OK, my su
On Do, 2015-04-09 at 08:50 +0200, Sebastian Berg wrote:
> Hi all,
>
> Let me take a shot at summing up some suggestions to make the indexing
> less surprising, and maybe we can gather some more in a more
> concentrated way now.
>
Did not want to comment on the first mail
> 1. Implement somethin
On Do, 2015-04-09 at 02:22 -0400, Nathaniel Smith wrote:
> On Wed, Apr 8, 2015 at 4:02 PM, Alan G Isaac wrote:
> > 1. I use numpy in teaching.
> > I have never heard a complaint about its indexing behavior.
> > Have you heard such complaints?
>
> Some observations:
>
> 1) There's an unrelated th
13 matches
Mail list logo
