Home Original page

BUG: Fix array_equal for numeric and non-numeric scalar types by eendebakpt · Pull Request #27275 · numpy/numpy

@eendebakpt

@eendebakpt

eendebakpt

@eendebakpt eendebakpt changed the title Draft: BUG: Fix array_equal for numeric and non-numeric scalar types BUG: Fix array_equal for numeric and non-numeric scalar types

Aug 23, 2024

@eendebakpt

mhvk

@eendebakpt

@eendebakpt

charris pushed a commit to charris/numpy that referenced this pull request

Aug 26, 2024 
Backport of numpy#27275

Mitigates numpy#27271. The underlying issue (an array comparison returning a
python bool instead of a numpy bool) is not addressed.

The order of statements is slightly reordered, so that the if
`a1 is a2:` check can be done before the calculation of
`cannot_have_nan`

Closes numpygh-27271

charris pushed a commit to charris/numpy that referenced this pull request

Aug 26, 2024 
Backport of numpy#27275

Mitigates numpy#27271. The underlying issue (an array comparison returning a
python bool instead of a numpy bool) is not addressed.

The order of statements is slightly reordered, so that the if
`a1 is a2:` check can be done before the calculation of
`cannot_have_nan`

Closes numpygh-27271

DimitriPapadopoulos pushed a commit to DimitriPapadopoulos/numpy that referenced this pull request

Aug 27, 2024 
…27275)

Mitigates numpy#27271. The underlying issue (an array comparison returning a python bool instead of a numpy bool) is not addressed.

The order of statements is slightly reordered, so that the if a1 is a2: check can be done before the calculation of cannot_have_nan

ArvidJB pushed a commit to ArvidJB/numpy that referenced this pull request

Nov 1, 2024 
…27275)

Mitigates numpy#27271. The underlying issue (an array comparison returning a python bool instead of a numpy bool) is not addressed.

The order of statements is slightly reordered, so that the if a1 is a2: check can be done before the calculation of cannot_have_nan