| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
* bump OpenBLAS version to 0.3.7.dev
in Azure CI to pick up AVX512 SkylakeX
fixes and match wheels
* use ctypes code to verify appropriate
version of OpenBLAS
|
|
|
|
|
|
|
|
|
|
| |
* Azure CI should no longer report
success when there are failures
outside of the test suite
* Azure CI will still always try
to publish test results, except
when a pipeline is manually cancelled
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* fail Azure CI after test publication
when there are test failures
|
|
|
|
|
|
|
| |
* add Azure configuration directives
to ensure that CI test results are
always published, even in the case
where there are test failures
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
* use pre-built openblas binary
for MacOS Azure CI builds to more
closely match the build scenario
used by numpy-wheels
* similarly, roll back gfortran
version to 4.9 to better match
wheel builds
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Test for DLL pollution in numpy/.libs/ in Azure
CI Windows Python 3.6 builds
* emit a warning with DLL names when > 1 are present
in numpy/.libs/
|
|
|
|
|
|
|
|
|
|
| |
* add an Azure CI test to mimic recent
Anaconda DLL path resolution restrictions
that prevent NumPy imports
* patch numpy.core initialization to use
absolute DLL path loading to overcome
the scenario described above
|
| |
|
|\
| |
| | |
TST: Use same OpenBLAS build for testing as for current wheels.
|
| | |
|
| | |
|
|\ \
| |/
|/| |
TEST: pin mingw version
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Always enable __array_function__ overrides.
- Remove special cases for Python 2 compatibility.
- Document these changes in 1.17.0-notes.rst.
It will be good to see ASV numbers to understand the performance implications
of these changes. If need be, we can speed up NumPy functions internally by
using non-dispatched functions (with ``.__wrapped__``).
|
|\ \
| | |
| | | |
BLD: move -std=c99 addition to CFLAGS to Azure config
|
| | |
| | |
| | |
| | | |
See gh-12610 for details.
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
* ported the refguide_check module from SciPy for usage
in NumPy docstring execution/ verification; added the
refguide_check run to Azure Mac OS CI
* adjusted NumPy docstrings such that refguide_check passes
|
| |
| |
| |
| |
| |
| |
| | |
* use the pre-built openblas binary
used for our 32-bit linux wheel builds
in our Azure development CI to reduce
dissonance with the wheels workflow
|
| |
| |
| |
| |
| |
| | |
* given the recent removal of Python 2.7
support / testing, we longer need the step
to install VC 9.0 in Azure Windows CI
|
|\ \
| | |
| | | |
TST: Azure Python version fix
|
| |/
| |
| |
| |
| |
| | |
* Azure test results are now published
with appropriate Python version
strings
|
|/
|
|
|
|
|
|
|
|
|
|
| |
- Create 1.17.0-notes
- Update index.rst for new notes
- Update pavement.py
- Update setup.py
- Remove Python 2.7 and 3.4 from CI testing.
- Add `# cython: language_level=3` to `*.pxd`, `*.pyx` files.
Note that this removes support for both Python2.7 and Python3.4 in
setup.py.
|
|
|
|
|
|
| |
* bump the version of openblas used
for Windows Azure CI testing to match
with wheel builds
|
| |
|
|
|
|
|
|
|
| |
* the Azure condition directive now
works just fine & is used in place
of a single-line jumble for Python
version checking in our CI now
|
| |
|
|
|
|
|
|
|
| |
* use vulture to check for unreachable Python
code paths in Azure CI
* fix up an unreachable path in f2py/capi_maps.py
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* attempt to replicate the 5 Appveyor
Windows CI entries on Azure service
* remove parallel testing from all Azure
jobs to improve reliability of our CI until
test suite is thread-safe
|
|
|