While trying to reproduce various fancy indexings for astropy's FITS
sections (a loaded-on-demand array), I found the following interesting
behavior:
>>> np.array([1])[..., 0]
array(1)
>>> np.array([1])[0]
1
>>> np.array([1])[(0,)]
1
The docs say "Ellipsis expand to the number of : objects needed
On 04/01/15 21:28, Sturla Molden wrote:
> A scientific paper or thesis should be written so it is completely
> reproducible. That would include describing the computer, OS, Python
> version and NumPy version, as well as C or Fortran compiler.
I completely agree and we should all work towards this
On 04/01/15 21:55, Sturla Molden wrote:
> On 03/01/15 20:49, Nathaniel Smith wrote:
>
>> OTOH the big problem that motivated his post was that his code is
>> all written against the APIs of the ancient and long-abandoned Numeric
>> project, and he finds the costs of transitioning them to the "new"
==
Announcing bcolz 0.7.3
==
What's new
==
This release includes the support for pickling persistent carray/ctable
objects contributed by Matthew Rocklin. Also, the included version of
Blosc is updated to ``v1.5.2``. Lastly, several minor issues an
On 03/01/15 20:49, Nathaniel Smith wrote:
> i.e., slow-incremental-change has actually worked well in his
> experience. (And in particular, the np.diagonal issue only comes in as
> an example to illustrate what he means by the phrase "slow continuous
> change" -- this particular change hasn't actu
On 04/01/15 17:22, Konrad Hinsen wrote:
> There are two different scenarios to consider here, and perhaps I didn't
> make that distinction clear enough. One scenario is that of a maintained
> library or application that depends on NumPy. The other scenario is a
> set of scripts written for a speci
Personally, I have never depended upon an implicit fill value. I would
always handle it explicitly. Off the top of my head, a project that might
have really good insight into how fill_value should work is the
python-netCDF4 project (so, talk to Jeff Whitaker, I think), and/or the
HDF5 people. I kno
On 03/01/15 20:49, Nathaniel Smith wrote:
> The post you cite brings this up explicitly:
>
> > [3] http://khinsen.wordpress.com/2014/09/12/the-state-of-numpy/
>
> I have huge respect for the problems and pain that Konrad describes in
> this blog post, but I really can't agree with the argument or
Hi Albert-Jan,
On Thu, Jan 1, 2015 at 8:57 PM, Albert-Jan Roskam wrote:
> Hi,
>
> I would like to use the numpy implementation for Pypy. In particular, I
> would like to use numpy.fromiter, which is available according to this
> overview: http://buildbot.pypy.org/numpy-status/latest.html. Howeve
On Sun, Jan 4, 2015 at 1:44 AM, Ralf Gommers wrote:
>
>
> On Sun, Jan 4, 2015 at 1:28 AM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Sat, Jan 3, 2015 at 4:54 PM, Sturla Molden
>> wrote:
>>
>>> On 03/01/15 03:04, Charles R Harris wrote:
>>>
>>> > The diag, diagonal, and
On Sat, Jan 3, 2015 at 11:08 PM, Charles R Harris wrote:
>
>
> On Sat, Jan 3, 2015 at 2:55 PM, Matthew Brett
> wrote:
>
>> Hi,
>>
>> On Thu, Jan 1, 2015 at 9:35 PM, Alexander Belopolsky
>> wrote:
>> > A discussion [1] is currently underway at GitHub which will benefit
>> from a
>> > larger foru
On Sun, Jan 4, 2015 at 1:28 AM, Charles R Harris
wrote:
>
>
> On Sat, Jan 3, 2015 at 4:54 PM, Sturla Molden
> wrote:
>
>> On 03/01/15 03:04, Charles R Harris wrote:
>>
>> > The diag, diagonal, and ravel functions have recently been changed to
>> > preserve subtypes. However, this causes lots of
12 matches
Mail list logo
