| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The comments in .travis.yml say
# After changing this file, check it on:
# http://lint.travis-ci.org/
When I do that, I get the following from the linter:
```
[warn] on root: unknown key "stage" (Comprehensive tests)
[info] on root: the key matrix is an alias for jobs, using jobs
[info] on root: missing os, using the default "linux"
```
This commit fixes the issues reported in those messages.
|
|
|
|
|
|
|
| |
Apart from the usual modifications, this
- Removes a release note snippet added after towncrier was run
- Removes testing on Python 3.5 as it is dropped for 1.19.x.
|
|
|
|
|
| |
- Use 3.8 instead of 3.8-dev
- Add some blank lines for clarity
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* for those cases where our CI uses an OpenBLAS backend
for testing it has now been updated to use v0.3.7 stable release
instead of a commit hash on the development branch preceding that
release
* the pre-built OpenBLAS binaries are pulled in from either the
MacPython ecosystem (most architectures) or from a custom build
script for ARMv8 and ppc64le architectures used on gcc compile farm machines
(documented in openblas_support module)
|
|
|
|
|
|
|
| |
Pytest-5.1.0 segfaults on python3.5-dbg. Because we will be
dropping 3.5 for NumPy 1.18 we might as well use Python3.6
for the debug testing. That cures the previous segfault,
but exposes another so we also pin pytest to 5.0.1.
|
| |
|
|
|
|
|
| |
* require OpenBLAS 0.3.7.dev in ARMv8
and POWER8 CI runs to match ecosystem / wheels
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* add a function to tools/openblas_support.py
that may be used to test OpenBLAS version
available through NumPy in a manner agnostic
to any specific CI service
* expand OpenBLAS version checking to include
ppc64le and POWER8 CI runs; a separate PR will
be provided to bump these versions to 0.3.7.dev
* OpenBLAS install was broken on ppc64le
Travis CI after migration to tools/openblas_support.py;
fixed that
* Azure CI config no longer uses a single-line
280-character Python "program" assigned to an
environment variable to check OpenBLAS version;
instead, it now leverages tools/openblas_support.py
to perform the same operation using a conventional
Python function
|
|
|
|
|
|
|
| |
Ubuntu 14.04 LTS (Trusty) provided a long term support distribution of
Ubuntu with a 5 year support window. This window ended in April 2019
and Trusty is now no longer supported. This commit removes Trusty from
the Travis-CI build.
|
| |
|
|\
| |
| | |
BLD: Allow users to specify BLAS and LAPACK library link order
|
| |
| |
| |
| | |
Signed-off-by: Nick Papior <nickpapior@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Also added a test to travis (apparently ATLAS=None... is not tested
on circleCI).
Signed-off-by: Nick Papior <nickpapior@gmail.com>
|
|/ |
|
|
|
| |
See blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- 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__``).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Per discussion on the mailing list, __array_function__ isn't quite ready to
release as part of NumPy 1.16:
https://mail.python.org/pipermail/numpy-discussion/2018-November/078949.html
We'd like to improve performance a bit, and it will be easier to support
introspection on NumPy functions if we support Python 3 only.
So for now, you need to set the environment variable
``NUMPY_EXPERIMENTAL_ARRAY_FUNCTION=1`` to enable dispatching.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Drop Python 3.4 testing on travis and appveyor.
* Move the DEBUG build to 3.5.
* Document dropping 3.4 support in the release notes.
|
|
|
|
|
|
|
|
|
|
| |
* DOC: errstate() and AppVeyor badge link
Removes outdated references to Python 2.5, which hasn't been
supported for several releases.
Corrected README.rst AppVeyor badge link.
* revert appveyor badge link to charris
|
|
|
|
|
| |
Add testing with Python 3.7 to both appveyor and travis.
|
| |
|
| |
|
| |
|
|\
| |
| | |
MAINT, TST: Fixes for Python 3.7
|
| |
| |
| |
| |
| | |
Cython 0.28.0 is out and should be compatible with the upcoming
Python 3.7, so start testing with that Python version.
|
|/
|
|
|
| |
Python 3.6 is more current and needs more testing than it is currently
getting. This is also useful preparation for droppping 2.7.
|
|
|
|
|
|
| |
The zesty release hit end of life Jan 13, 2018 and it seems that travis
ci tests are failing due to a failure to fetch it. This updates to use
artful. When the bionic LTS comes out in April, we should update again.
|
| |
|
| |
|
|
|
|
| |
They are not worth two seperate slow test runs.
|
| |
|
|
|
|
|
|
|
| |
Setting NPY_RELAXED_STRIDES_DEBUG=1 in the enviroment when relaxed
stride checking is enabled will cause numpy to be compiled with affected
strides set to bogus values in order to help smoke out incorrect usage
of strides in downstream projects.
|
| |
|
|\
| |
| | |
MAINT: Rebuild lapack lite
|
| | |
|
| |
| |
| |
| |
| | |
newer gcc, python, cython...
update eatmydata setting for new paths and earlier usage during chroot setup
|
|/ |
|
|
|
|
|
|
| |
When python is invoked with switch -3, it emits waring "classic int division"
for strict integer divisions. The same behavior is now implemented to numpy
with this fix
|
|
|
|
|
|
|
| |
With USE_DEBUG=1, the wrong python was being used
to create the virtualenv, meaning that installed
packages (e.g. Cython) were being installed to
the wrong location.
|
| |
|