|
On 04/11/17 18:00,
numpy-discussion-requ...@python.org wrote:
Date: Fri, 3 Nov 2017 20:56:38 -0600 From: Charles R Harris <charlesr.har...@gmail.com> To: numpy-discussion <numpy-discussion@python.org> Subject: [Numpy-discussion] NumPy 1.14 branch. Message-ID: <CAB6mnxL7=swsmzb1sujpresawhznxj4qcazhywqw+6mxvoz...@mail.gmail.com> Content-Type: text/plain; charset="utf-8"Hi All, I'd like to branch NumPy 1.14 soon. Before doing so, I'd like to make sure at a minimum that 1) Changes in array print formatting are done. 2) Proposed deprecations have been make. If there are other things that folks see as essential, now is the time to speak up. Chuckn I would like to get some help with review/merge of the UPDATEIFCOPY deprecation in https://github.com/numpy/numpy/pull/9639 It deprecates resolving UPDATEIFCOPY semantics in the ndarray __dealloc__, which makes the resolution less magical and also makes NumPy compliant with non-refcount garbage collection strategies (like PyPy's GC). The thought is to warn in Numpy 1.14, and remove in 1.15, so if we miss this milestone it might be a while until one clear pain point with PyPy can be resolved. Matti |
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
