[Numpy-discussion] next NumPy triage meeting

2023-07-09 Thread Inessa Pawson
The next NumPy triage meeting will be held this Wednesday, July 13th at 5pm UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVXZz09 . Everyone is welcome to attend and contribu

[Numpy-discussion] Re: mixed mode arithmetic

2023-07-09 Thread glaserj--- via NumPy-Discussion
Neal Becker wrote: > I've been browsing the numpy source. I'm wondering about mixed-mode > arithmetic on arrays. I believe the way numpy handles this is that it > never does mixed arithmetic, but instead converts arrays to a common type. > Arguably, that might be efficient for a mix of say, doub

[Numpy-discussion] Feature: Imporved specificity in exceptions raised by random.seed()

2023-07-09 Thread David Thrower
When a number is passed to random.seed(), which is otherwise numerically valid, but is of the wrong data type (e.g. a string passed into a Flask app that was not cast to an int type or perhaps a float), a VauleError is raised with an ambiguous caption: `The value [...] cannot be used to seed a

[Numpy-discussion] Re: mixed mode arithmetic

2023-07-09 Thread Matti Picus
On 9/7/23 23:34, glaserj--- via NumPy-Discussion wrote: Reviving this old thread - I note that numpy.dot supports in-place computation for performance reasons like this c = np.empty_like(a, order='C') np.dot(a, b, out=c) However, the data type of the pre-allocated c array must match the result