Hi all,
Now that I'm in write-long-emails-about-$$ mode, I'll continue with: IBM
just posted at $5500 bounty on BountySource for adding VSX (= PowerPC
equivalent of SSE/AVX SIMD instructions we have for x86) support to NumPy:
https://github.com/numpy/numpy/issues/13393.
This is an interesting exp
Hi all,
On behalf of the NumPy Steering Council I'm happy to announce that we now
have an agreement between Tidelift and NumFOCUS for NumPy. The summary of
the agreement is: Tidelift will pay NumPy a minimum of $1000/month until
Oct 2020, and NumPy will do the following:
- provide a documented way
Hi,
There will be a NumPy community meeting at 12 pm Pacific Time on April 24/
2019.
Anyone is welcome to join & edit the meeting notes available here:
https://hackmd.io/a03zhF4TSsewJp_fXXXwOQ?view
___
NumPy-Discussion mailing list
NumPy-Discussion@pyth
On Tue, Apr 23, 2019 at 4:31 PM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> Hi All,
>
> Reading the discussion again, I've gotten somewhat unsure that it is
> helpful to formalize a way to call an implementation that we can and
> hopefully will change. Why not just leave it at __wrap
Hi All,
Reading the discussion again, I've gotten somewhat unsure that it is
helpful to formalize a way to call an implementation that we can and
hopefully will change. Why not just leave it at __wrapped__? I think the
name is no worse and it is more obvious that one relies on something
private.
And hopefully last update: 0.9.1 is now also released, with an update to
install_requires. Numpydoc now requires Sphinx >= 1.6.5
On Sun, Apr 21, 2019 at 9:35 PM Ralf Gommers wrote:
>
>
> On Sun, Apr 21, 2019 at 9:01 PM Ralf Gommers
> wrote:
>
>> Hi all,
>>
>> Numpydoc 0.9.0 was just released.
On Mon, Apr 22, 2019 at 11:13 PM Stephan Hoyer wrote:
>
>> On Mon, Apr 22, 2019 at 9:26 PM Nathaniel Smith wrote:
>>>
>>> Your last email didn't really clarify anything for me. I get that
>>> np.func.__numpy_implementation__ is intended to have the semantics of
>>> numpy's implementation of fun
