<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/numpy.git/numpy/core, branch v1.20.0</title>
<subtitle>github.com: numpy/numpy.git
</subtitle>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/'/>
<entry>
<title>Update numpy/core/src/multiarray/mapping.c</title>
<updated>2021-01-29T21:14:06+00:00</updated>
<author>
<name>Sebastian Berg</name>
<email>sebastian@sipsolutions.net</email>
</author>
<published>2021-01-29T20:17:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=f3070c5569f2bccc232d8c792a11b6340f5c9e6b'/>
<id>f3070c5569f2bccc232d8c792a11b6340f5c9e6b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: Ensure too many advanced indices raises an exception</title>
<updated>2021-01-29T21:13:50+00:00</updated>
<author>
<name>Sebastian Berg</name>
<email>sebastian@sipsolutions.net</email>
</author>
<published>2021-01-11T18:02:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=436aec562ff372e2832df26068f35a4f5554dba5'/>
<id>436aec562ff372e2832df26068f35a4f5554dba5</id>
<content type='text'>
The number of indices is limited to 2*MAXDIMS currently to allow
mixing integer indices, e.g. with new indices `np.newaxis` (one
removes output dimensions, the other adds new ones).
This means that more than MAXDIMS advanced indices can be passed
on to the advanced indexing machinery (`MapIterNew`), which did
not check for this possibility.

Closes gh-18145
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The number of indices is limited to 2*MAXDIMS currently to allow
mixing integer indices, e.g. with new indices `np.newaxis` (one
removes output dimensions, the other adds new ones).
This means that more than MAXDIMS advanced indices can be passed
on to the advanced indexing machinery (`MapIterNew`), which did
not check for this possibility.

Closes gh-18145
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: Keep ignoring most errors during array-protocol lookup</title>
<updated>2021-01-21T02:03:48+00:00</updated>
<author>
<name>Sebastian Berg</name>
<email>sebastian@sipsolutions.net</email>
</author>
<published>2021-01-20T21:29:21+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=dff151ea59bab71c5fa88df7e11bf6ec7c7fa12c'/>
<id>dff151ea59bab71c5fa88df7e11bf6ec7c7fa12c</id>
<content type='text'>
Closes (the later point) in gh-17965 and reverts parts of
gh-17817.
Shapely did rely on being able to raise a NotImplementedError
which then got ignored in the attribute lookup.
Arguably, this should probably just raise an AttributeError to
achieve that behaviour, but it means we can't just rip the band-aid
off here.

Since 1.20 is practically released, just reverting most of the change
(leaving only recursion and memory error which are both arguably
pretty fatal).
Ignoring most errors should be deprecated (and I am happy to do so),
but it is not important enough for 1.20 or very important in itself.

Closes gh-17965
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Closes (the later point) in gh-17965 and reverts parts of
gh-17817.
Shapely did rely on being able to raise a NotImplementedError
which then got ignored in the attribute lookup.
Arguably, this should probably just raise an AttributeError to
achieve that behaviour, but it means we can't just rip the band-aid
off here.

Since 1.20 is practically released, just reverting most of the change
(leaving only recursion and memory error which are both arguably
pretty fatal).
Ignoring most errors should be deprecated (and I am happy to do so),
but it is not important enough for 1.20 or very important in itself.

Closes gh-17965
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: Promotion between strings and objects was assymetric</title>
<updated>2021-01-11T22:17:02+00:00</updated>
<author>
<name>Sebastian Berg</name>
<email>sebastian@sipsolutions.net</email>
</author>
<published>2021-01-11T18:51:45+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=3710d9aa30ecf61fb1f7db5163c77cb1c12107c3'/>
<id>3710d9aa30ecf61fb1f7db5163c77cb1c12107c3</id>
<content type='text'>
After an unrelated fix, the logic for string and object promotion
was incorrect briefly, this fixes it to be correct (symmetric).
Before, string and unicode would return that
`string.__common_dtype(object)` is in fact `string`, which is of
course incorrect. (since `object.__common_dtype__(other)` always
returns `object` this depended on the order, and the NumPy tests
apparently did only test the opposite direction (or nothing).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
After an unrelated fix, the logic for string and object promotion
was incorrect briefly, this fixes it to be correct (symmetric).
Before, string and unicode would return that
`string.__common_dtype(object)` is in fact `string`, which is of
course incorrect. (since `object.__common_dtype__(other)` always
returns `object` this depended on the order, and the NumPy tests
apparently did only test the opposite direction (or nothing).
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG, MAINT: improve avx512 mask logical operations</title>
<updated>2021-01-10T15:19:49+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2021-01-05T06:46:02+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=3092b0aeee616708d02b9c6f060980678538b33c'/>
<id>3092b0aeee616708d02b9c6f060980678538b33c</id>
<content type='text'>
  It also fixes conversion warning between `__mmask16` and `__mmask8`
  on msvc2019 when logical intrinsics of AVX512DQ are available.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  It also fixes conversion warning between `__mmask16` and `__mmask8`
  on msvc2019 when logical intrinsics of AVX512DQ are available.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: Fix promotion of half and string</title>
<updated>2021-01-06T13:40:39+00:00</updated>
<author>
<name>Sebastian Berg</name>
<email>sebastian@sipsolutions.net</email>
</author>
<published>2021-01-05T04:48:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=3be85af32db5d8d1aefdc02c4af4ee5be6b96aec'/>
<id>3be85af32db5d8d1aefdc02c4af4ee5be6b96aec</id>
<content type='text'>
I somehow managed to miss that half breaks the order of dtypes and
has a higher number than the strings. Could be backported, but it
doesn't really matter, since it only makes a difference if the
compile time flag is used and even then is pretty fringe.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I somehow managed to miss that half breaks the order of dtypes and
has a higher number than the strings. Could be backported, but it
doesn't really matter, since it only makes a difference if the
compile time flag is used and even then is pretty fringe.
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG, SIMD: Fix _simd module build for 64bit ARM/NEON clang</title>
<updated>2021-01-05T14:36:46+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2020-12-29T02:01:12+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=793241c6de4d3852a5fc59e07e5ae5a43c5c8572'/>
<id>793241c6de4d3852a5fc59e07e5ae5a43c5c8572</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>MAINT, BLD: few tweaks in the comments and log message</title>
<updated>2021-01-03T18:53:19+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2021-01-02T06:30:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=45177eaa3d2a2823bb19b2aa46486e2e1caa7c11'/>
<id>45177eaa3d2a2823bb19b2aa46486e2e1caa7c11</id>
<content type='text'>
Co-authored-by: Matti Picus &lt;matti.picus@gmail.com&gt;
Co-authored-by: h-vetinari &lt;h.vetinari@gmx.com&gt;
Co-authored-by: Derek Homeier &lt;dhomeie@gwdg.de&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Co-authored-by: Matti Picus &lt;matti.picus@gmail.com&gt;
Co-authored-by: h-vetinari &lt;h.vetinari@gmx.com&gt;
Co-authored-by: Derek Homeier &lt;dhomeie@gwdg.de&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG, BLD: Generate the main dispatcher config header into the build dir</title>
<updated>2021-01-03T18:52:44+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2020-12-30T10:15:55+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=9406bce00576ba60128b08324fa8a2ad69458e41'/>
<id>9406bce00576ba60128b08324fa8a2ad69458e41</id>
<content type='text'>
  The new path becomes `build/src.*/numpy/distutils/include/npy_cpu_dispatch_config.h`
  instead of `numpy/core/src/common/_cpu_dispatch.h`.

  The new path allows other projects to re-use the CPU dispatcher
  once we decide to expose the following headers:
    - `numpy/core/src/common/npy_cpu_dispatch.h`
    - `numpy/core/src/common/npy_cpu_features.h`
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  The new path becomes `build/src.*/numpy/distutils/include/npy_cpu_dispatch_config.h`
  instead of `numpy/core/src/common/_cpu_dispatch.h`.

  The new path allows other projects to re-use the CPU dispatcher
  once we decide to expose the following headers:
    - `numpy/core/src/common/npy_cpu_dispatch.h`
    - `numpy/core/src/common/npy_cpu_features.h`
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: Fix concatenation when the output is "S" or "U"</title>
<updated>2020-12-23T22:04:03+00:00</updated>
<author>
<name>Sebastian Berg</name>
<email>sebastian@sipsolutions.net</email>
</author>
<published>2020-12-21T22:46:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=4bd709c0fde357811c63bcd5387e7b86f1780751'/>
<id>4bd709c0fde357811c63bcd5387e7b86f1780751</id>
<content type='text'>
Previously, the dtype was used, this now assumes that we want to
cast to a string of (unknown) length.  This is a simplified version
of what happens in `np.array()` or `arr.astype()` (it does never
inspect the values, e.g. for object casts).

This is more complex as I would like, and with the refactor of
ResultType and similar can be cleaned up a bit more hopefully.

Note that currently, object to "S" or "U" casts simply return
length 64 strings, but with the new version, this will be an error
(although the error message probably needs improvement).
This is a behaviour inherited from other places however.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Previously, the dtype was used, this now assumes that we want to
cast to a string of (unknown) length.  This is a simplified version
of what happens in `np.array()` or `arr.astype()` (it does never
inspect the values, e.g. for object casts).

This is more complex as I would like, and with the refactor of
ResultType and similar can be cleaned up a bit more hopefully.

Note that currently, object to "S" or "U" casts simply return
length 64 strings, but with the new version, this will be an error
(although the error message probably needs improvement).
This is a behaviour inherited from other places however.
</pre>
</div>
</content>
</entry>
</feed>
