Hi All,
The middle of May seems about right for branching 1.17.x and making the
first rc. I'm happy to make the release, but if someone else would like to
give it a try that would be great.
Chuck
___
NumPy-Discussion mailing list
Hi All,
I'm planning on releasing 1.16.3 this weekend. There will be more
maintenance releases, but if there is something important that you think
needs to be in this release, please respond to this email.
Chuck
___
NumPy-Discussion mailing list
Hi All,
There will be a community meeting tomorrow, April 17, at 12 pm Pacific Time.
Anyone may join & contribute to the work in progress meeting document
available here: https://hackmd.io/a03zhF4TSsewJp_fXXXwOQ?view
Best wishes,
Tyler
___
__numpy_implementation__ is indeed simply a slot for third-parties to
access NumPy's implementation. It should be considered "NumPy's current
implementation", not "NumPy's implementation as of 1.14". Of course, in
practice these will remain very similar, because we are already very
conservative
On Tue, Apr 16, 2019 at 11:19 AM Paul Hobson wrote:
> On Tue, Apr 16, 2019 at 8:32 AM Chris Barker - NOAA Federal <
> chris.bar...@noaa.gov> wrote:
>
>> Another consideration is that some organizations, the US federal
>> government, for instance, cannot make donations. I wouldn’t be surprised if
On Tue, Apr 16, 2019 at 8:32 AM Chris Barker - NOAA Federal <
chris.bar...@noaa.gov> wrote:
> Another consideration is that some organizations, the US federal
> government, for instance, cannot make donations. I wouldn’t be surprised if
> some Universities might have similar restrictions on using
I somewhat share Nathaniel's worry that by providing
`__numpy_implementation__` we essentially get stuck with the
implementations we have currently, rather than having the hoped-for freedom
to remove all the `np.asarray` coercion. In that respect, an advantage of
using `_wrapped` is that it is
