On Mon, Jul 23, 2018 at 3:24 PM, Matti Picus wrote:
> On 19/07/18 14:08, Charles R Harris wrote:
>
>> Hi All,
>>
>> The NumPy Steering Council has been looking at commit rights for the
>> NumPy developers hired at BIDS. We would like them to be able to label PRs,
>> close issues, and merge simple
On 19/07/18 14:08, Charles R Harris wrote:
Hi All,
The NumPy Steering Council has been looking at commit rights for the
NumPy developers hired at BIDS. We would like them to be able to label
PRs, close issues, and merge simple fixes; doing that requires commit
privileges. OTOH, it is also the
On Mon, Jul 23, 2018 at 1:45 PM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> That sentence I think covers it very well. Subclasses can and should be
> expected to evolve along with numpy, and if that means some numpy-version
> dependent parts, so be it (we have those now...).
>
My ho
>
>
> Rather, we might state that "At some point in the future, the NumPy
> development team may no longer interested in maintaining workarounds for
> specific subclasses, because other interfaces for extending NumPy are
> believed to be more maintainable/preferred."
>
> That sentence I think cover
On Sun, Jul 22, 2018 at 12:28 PM Ralf Gommers
wrote:
> Then, I think it's not unreasonable to draw a couple of hard lines. For
> example, removing complete submodules like linalg or random has ended up on
> some draft brainstorm roadmap list because someone (no idea who) put it
> there after a si
On Sun, Jul 22, 2018 at 12:28 PM Ralf Gommers
wrote:
> In particular, I'd like every deprecation message to say "this deprecated
> feature will be removed by release X.Y.0". At the moment we don't do that,
> so if users see a message they don't know if a removal will happen next
> year, in the f
On Sat, Jul 21, 2018 at 6:40 PM Marten van Kerkwijk <
m.h.vankerkw...@gmail.com> wrote:
> But I think the subclassing section is somewhat misleading in suggesting
> `ndarray` is not well designed to be subclassed. At least, for neither my
> work on Quantity nor that on MaskedArray, I've found that
Congratulations to Antony for his hard work on this important backend!
As far as I am concerned, the cairo backend is the future of matplotlib.
Test this backend out for yourselves and help us take matplotlib to the
next level in high-quality charting!
Cheers!
Ben Root
On Sun, Jul 22, 2018 at 4:
On Mon, Jul 23, 2018 at 11:21 AM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
> Hi All,
>
> On behalf of the NumPy team I'm pleased to announce the release of NumPy
> 1.15.0rc2.
>
Oops, NumPy 1.15.0. Oh well ...
This release has an unusual number of cleanups, many deprecations of old
>
Hi All,
On behalf of the NumPy team I'm pleased to announce the release of NumPy
1.15.0rc2.
This release has an unusual number of cleanups, many deprecations of old
functions,
and improvements to many existing functions. A total of 438 pull reguests
were merged
for this release, please look at the
10 matches
Mail list logo
