The rationale for the change allowing that construction was twofold: it's
easier to understand what has gone wrong when seeing the `list`s in the
repr than it was from the cryptic error message; and there were some jagged
cases that already succeeded in this way, and it was less confusing to be
con
On 27/12/18 3:21 am, Benjamin Root wrote:
Ewww, kinda wish that would be an error... It would be too easy for a
typo to get accepted this way.
On Wed, Dec 26, 2018 at 1:59 AM Eric Wieser
mailto:wieser.eric%2bnu...@gmail.com>>
wrote:
In the latest version of numpy, this runs without an e
Ewww, kinda wish that would be an error... It would be too easy for a typo
to get accepted this way.
On Wed, Dec 26, 2018 at 1:59 AM Eric Wieser
wrote:
> In the latest version of numpy, this runs without an error, although may
> or may not be what you want:
>
> In [1]: np.array([[1,2],[[1,2],[3,
On Wed, Dec 26, 2018 at 3:29 PM Sebastian Berg
wrote:
> Hi all,
>
> In https://github.com/numpy/numpy/pull/11897 I am looking into the
> addition of a `copy=np.never_copy` argument to:
> * np.array
> * arr.reshape/np.reshape
> * arr.astype
>
> Which would cause an error to be raised when nu
I am pleased to announce release 2018.4 of SfePy.
Description
---
SfePy (simple finite elements in Python) is a software for solving systems of
coupled partial differential equations by the finite element method or by the
isogeometric analysis (limited support). It is distributed under t
Hi all,
In https://github.com/numpy/numpy/pull/11897 I am looking into the
addition of a `copy=np.never_copy` argument to:
* np.array
* arr.reshape/np.reshape
* arr.astype
Which would cause an error to be raised when numpy cannot guarantee
that the returned array is a view of the input arra
