<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/python-packages/numpy.git/numpy/distutils/command/build_ext.py, branch v1.23.2</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>Fix build_ext interaction with non numpy extensions</title>
<updated>2022-01-28T18:45:38+00:00</updated>
<author>
<name>serge-sans-paille</name>
<email>serge.guelton@telecom-bretagne.eu</email>
</author>
<published>2022-01-28T18:45:38+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=7764452b738cf7e55e68fdbb935400d56926007d'/>
<id>7764452b738cf7e55e68fdbb935400d56926007d</id>
<content type='text'>
Numpy extensions define the extra_cxx_compile_args and extra_c_compile_args
filed, but distutils extensions don't. Take that into account when populating
build_extension.

Should fix #20928
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Numpy extensions define the extra_cxx_compile_args and extra_c_compile_args
filed, but distutils extensions don't. Take that into account when populating
build_extension.

Should fix #20928
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: distutils: fix building mixed C/Fortran extensions</title>
<updated>2022-01-24T11:30:21+00:00</updated>
<author>
<name>Ralf Gommers</name>
<email>ralf.gommers@gmail.com</email>
</author>
<published>2022-01-24T11:30:21+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=1e83f8355336bd722af3ae2608735fa53218ece9'/>
<id>1e83f8355336bd722af3ae2608735fa53218ece9</id>
<content type='text'>
In SciPy we had a couple of cases where we build a Python extension
with C source files but linked against static libraries built from
Fortran code. Those should be using the Fortran linker, but this
was broken in 1.22.0 by gh-19713 (the PR that introduced C++ in NumPy).

This fixes a few issues in the `build_ext` command, and documents better
what is going on there.

Should close SciPy issues 8325 and 15414.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
In SciPy we had a couple of cases where we build a Python extension
with C source files but linked against static libraries built from
Fortran code. Those should be using the Fortran linker, but this
was broken in 1.22.0 by gh-19713 (the PR that introduced C++ in NumPy).

This fixes a few issues in the `build_ext` command, and documents better
what is going on there.

Should close SciPy issues 8325 and 15414.
</pre>
</div>
</content>
</entry>
<entry>
<title>[demo] how-to replacing numpy custom generation engine by raw C++</title>
<updated>2021-10-22T09:57:28+00:00</updated>
<author>
<name>serge-sans-paille</name>
<email>serge.guelton@telecom-bretagne.eu</email>
</author>
<published>2021-08-19T07:28:09+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=2ae7aeb3aa909b1a16bc58fd0e40dc4476dff35d'/>
<id>2ae7aeb3aa909b1a16bc58fd0e40dc4476dff35d</id>
<content type='text'>
This is just a technical prototype to measure and discuss the impact and
implication of moving to C++ for kernel code generation.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This is just a technical prototype to measure and discuss the impact and
implication of moving to C++ for kernel code generation.
</pre>
</div>
</content>
</entry>
<entry>
<title>DOC: Typos found by codespell</title>
<updated>2021-09-21T18:29:43+00:00</updated>
<author>
<name>Dimitri Papadopoulos</name>
<email>3234522+DimitriPapadopoulos@users.noreply.github.com</email>
</author>
<published>2021-09-21T07:18:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=83960267dc097742cb67ef575504afa56f82b102'/>
<id>83960267dc097742cb67ef575504afa56f82b102</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>BLD, BUG: Fix bdist_wheel duplicate building</title>
<updated>2021-05-05T10:25:42+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2021-05-05T10:11:28+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=d3e666c94230d4b45b9736103446f8b526ef426a'/>
<id>d3e666c94230d4b45b9736103446f8b526ef426a</id>
<content type='text'>
  The bug can occur only if the build option `build`
  was passed before the option `bdist_wheel`.

  You may still realize a duplicate printing for the compiler
  optimization report in the build log, which is normal due to
  multiple calling of command `build` by setuptools.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  The bug can occur only if the build option `build`
  was passed before the option `bdist_wheel`.

  You may still realize a duplicate printing for the compiler
  optimization report in the build log, which is normal due to
  multiple calling of command `build` by setuptools.
</pre>
</div>
</content>
</entry>
<entry>
<title>BLD, BUG: Fix compiler optimization log AttributeError</title>
<updated>2021-05-04T06:49:01+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2021-05-04T06:00:48+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=034aedc545c03417c0dae1b20c84098459c4b3a4'/>
<id>034aedc545c03417c0dae1b20c84098459c4b3a4</id>
<content type='text'>
  The error appears when option `build` is represented
  before `bdist_wheel`.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  The error appears when option `build` is represented
  before `bdist_wheel`.
</pre>
</div>
</content>
</entry>
<entry>
<title>ENH, SIMD: Add support for dispatching C++ sources</title>
<updated>2021-04-22T21:11:45+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2021-04-22T19:35:53+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=2d9e75f3a1dbe21de6b53cd2996e45054d3b86c5'/>
<id>2d9e75f3a1dbe21de6b53cd2996e45054d3b86c5</id>
<content type='text'>
    Same usage as the C dispatch-able sources except files extensions
    should be `.dispatcher.cpp` or `.dispatch.cxx` rather than `.dispatch.c`
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
    Same usage as the C dispatch-able sources except files extensions
    should be `.dispatcher.cpp` or `.dispatch.cxx` rather than `.dispatch.c`
</pre>
</div>
</content>
</entry>
<entry>
<title>BUG: don't mutate list of fake libraries while iterating over it (#18295)</title>
<updated>2021-02-04T19:13:39+00:00</updated>
<author>
<name>Nicholas McKibben</name>
<email>nicholas.bgp@gmail.com</email>
</author>
<published>2021-02-04T19:13:39+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=d3763198673ffc1092539041b8bd23134ae22bee'/>
<id>d3763198673ffc1092539041b8bd23134ae22bee</id>
<content type='text'>
* BUG: don't mutate list of fake libraries while iterating over it

* BUG: iterate over copy of list

* TST: add build test for build_ext fix (#1)

* TST: add build test for build_ext fix

* TST: clearer test name

* STY: use triple quotes instead of lists of strings

* FIX: check for f77 compiler before test is run

* DOC: add comment explaining that a list copy is necessary</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
* BUG: don't mutate list of fake libraries while iterating over it

* BUG: iterate over copy of list

* TST: add build test for build_ext fix (#1)

* TST: add build test for build_ext fix

* TST: clearer test name

* STY: use triple quotes instead of lists of strings

* FIX: check for f77 compiler before test is run

* DOC: add comment explaining that a list copy is necessary</pre>
</div>
</content>
</entry>
<entry>
<title>BUG, BLD: Generate the main dispatcher config header into the build dir</title>
<updated>2021-01-03T05:36:30+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=caec7f21ce3ca2672e93781a379734295c00debe'/>
<id>caec7f21ce3ca2672e93781a379734295c00debe</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>ENH: Expose the NumPy C SIMD vectorization interface "NPYV" to Python</title>
<updated>2020-10-27T11:46:58+00:00</updated>
<author>
<name>Sayed Adel</name>
<email>seiko@imavr.com</email>
</author>
<published>2020-07-08T07:27:13+00:00</published>
<link rel='alternate' type='text/html' href='http://git.baserock.org/cgit/delta/python-packages/numpy.git/commit/?id=cb3efe8e03b53dbab457a99be1a48384312abe16'/>
<id>cb3efe8e03b53dbab457a99be1a48384312abe16</id>
<content type='text'>
  '_simd' is a new module to bring the NumPy C SIMD vectorization interface "NPYV"

  The module is designed to be extremely flexible so that it can accommodate any kind
  intrinsics, also to generate a python interface almost similar to the C interface.

  The main purpose of this module is to test NPYV intrinsics in python,
  but still can be used as an effective solution in designing SIMD kernels.

  Also add a new command-line argument `--simd-test` to control of targeted CPU features
  for the `_simd` module.

Co-authored-by: Matti Picus &lt;matti.picus@gmail.com&gt;
Co-authored-by: Eric Wieser &lt;wieser.eric@gmail.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
  '_simd' is a new module to bring the NumPy C SIMD vectorization interface "NPYV"

  The module is designed to be extremely flexible so that it can accommodate any kind
  intrinsics, also to generate a python interface almost similar to the C interface.

  The main purpose of this module is to test NPYV intrinsics in python,
  but still can be used as an effective solution in designing SIMD kernels.

  Also add a new command-line argument `--simd-test` to control of targeted CPU features
  for the `_simd` module.

Co-authored-by: Matti Picus &lt;matti.picus@gmail.com&gt;
Co-authored-by: Eric Wieser &lt;wieser.eric@gmail.com&gt;
</pre>
</div>
</content>
</entry>
</feed>
