Re: [Numpy-discussion] Splitting MaskedArray into a separate package

2018-05-24 Thread Allan Haldane
On 05/24/2018 11:31 AM, Sebastian Berg wrote:

> I also somewhat like the idea of taking it out (once we have a first
> replacement) in the case that we have a plan to do a better/lower level
> replacement at a later point within numpy.
> Removal generally has its merits, but if a (mid term) replacement will
> come in any case, it would be nice to get those started first if
> possible.
> Otherwise downstream might end up having to fix up things twice.
> 
> - Sebastian

Yes, I think the way forward is to start working on a new masked array
while keeping the old one in place.

Once it has progressed a little and we can step back and look at it, we
can consider how to switch over. I imagine we would have both present in
numpy under different names for a while.

Also, I think it would be nice to work on it soon because it is a chance
for us to eat our own dogfood in the __array_ufunc__ interface, which is
not yet set in stone so we can fix any problems we discover with it.

Allan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] NumPy sprint May 24-25 at BIDS

2018-05-24 Thread Stefan van der Walt
Hi Jaime,

On Thu, 24 May 2018 10:01:40 -0700, Jaime Fernández del Río wrote:
> I will be there tomorrow for sure, though. What time do you plan on
> starting?

Thanks for the heads-up.  We'll probably start around 9:30am.  We're at
190 Doe Library on Berkeley campus.

We started today by discussing how a draft roadmap could look; I'll post
a more detailed update after the sprint.

Best regards,
Stéfan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Citation for ndarray

2018-05-24 Thread Stefan van der Walt
Hi Nathan,

On Thu, 24 May 2018 13:13:16 -0500, Nathan Goldbaum wrote:
> I see listed on the scipy.org site that the preferred citation for NumPy is
> the "Guide to NumPy":
> 
> https://www.scipy.org/citing.html
> 
> This could work for what I'm writing, but I'd prefer to find a citation
> specifically for NumPy's ndarray data structure. Does such a citation
> exist?

The citation used to point to "The NumPy array: a structure for
efficient numerical computation" (https://arxiv.org/abs/1102.1523), but
I asked that it be changed to give credit to Travis.

I am not aware of publications for the original Numeric and NumArray;
the first reference for NumPy itself is Travis's book.

Best regards,
Stéfan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion


[Numpy-discussion] Citation for ndarray

2018-05-24 Thread Nathan Goldbaum
Hi all,

I see listed on the scipy.org site that the preferred citation for NumPy is
the "Guide to NumPy":

https://www.scipy.org/citing.html

This could work for what I'm writing, but I'd prefer to find a citation
specifically for NumPy's ndarray data structure. Does such a citation exist?

Thanks!

-Nathan
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] Splitting MaskedArray into a separate package

2018-05-24 Thread Sebastian Berg
On Wed, 2018-05-23 at 23:48 +0200, Sebastian Berg wrote:
> On Wed, 2018-05-23 at 17:33 -0400, Allan Haldane wrote:



> 
> If we do not plan to replace it within numpy, we need to discuss a
> bit
> how it might affect infrastructure (multiple implementations).
> 
> There is the other discussion about how to replace it. By opening
> up/creating new masked dtypes or similar (cool but unclear how
> complex/long term) or `__array_ufunc__` based (relatively simple,
> will
> get rid of the nastier hacks that are currently needed).
> 
> Or even both, just on different time scales?
> 

I also somewhat like the idea of taking it out (once we have a first
replacement) in the case that we have a plan to do a better/lower level
replacement at a later point within numpy.
Removal generally has its merits, but if a (mid term) replacement will
come in any case, it would be nice to get those started first if
possible.
Otherwise downstream might end up having to fix up things twice.

- Sebastian


> My first gut feeling about the proposal is: I love the idea to get
> rid
> of it... but lets not do it, it does feel like it makes too much
> infrastructure unclear.
> 
> - Sebastian
> 
> 
> > 
> > Allan
> > 
> > 
> > ___
> > NumPy-Discussion mailing list
> > NumPy-Discussion@python.org
> > https://mail.python.org/mailman/listinfo/numpy-discussion
> 
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion

signature.asc
Description: This is a digitally signed message part
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion