| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use `set -ex` in tools/travis-before-install.sh.
* Install build dependencies in tools/travis-before-install.sh.
* Update a comment about an additional option in CFLAGS when USE_DEBUG=1.
* Clear PYTHONOPTIMIZE when running `pip install -r test_requirements.txt`
because version 2.19 of pycparser (a dependency of one of the packages
in test_requirements.txt) does not provide a wheel, and the source tar
file does not install correctly when Python's optimization level is set
to strip docstrings (see https://github.com/eliben/pycparser/issues/291).
* Remove unnecessary calls of `pip install` in tools/travis-test.sh.
Closes gh-15108.
|
| | |
|
| |
|
|
|
| |
- Use 3.8 instead of 3.8-dev
- Add some blank lines for clarity
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
MAINT: Avoid BytesWarning in PyArray_DescrConverter()
|
| | |
| |
| |
| |
| |
| |
| |
| | |
A BytesWarning can be emitted when bytes are and strings are mismatched.
Catching BytesWarning ensures a better boundary between str and bytes
type. The test suite is now run with the -b flag to emit this warning.
Fixes #9308
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This is (hopefully) temporary. Current versions of pytest abort
when this flag is passed and the tests run with python3.6-dbg.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
|
|
|
| |
* replace usage of test-installed-numpy.py
with runtests.py; they serve similar purposes
and the latter is more commonly used / maintained
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
* Travis CI will now fail NumPy builds
at the compilation stage when
implicit-function-declaration is detected;
otherwise, C functions without included prototypes
may be allowed to pass through with a warning
|
| |
|
|
|
|
|
|
|
|
| |
- 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__``).
|
| |
|
|
|
|
|
| |
Most of this was already done, but we were still raising an error for
declaration after a statement because the Windows Python 2.7 compiler
did not allow it. We can fix this now as NumPy >= 1.17 has dropped
Python 2.7 support.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
* our CI should now report test
coverage for the new array_function
dispatch protocol
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
[skip appveyor]
C99 looks to work with gcc for all the Python versions we currently
support. Testing with c99 is a step forward in testing #11888 before
it gets merged after we drop Python 2.7 support.
|
| |
|
|
|
|
| |
* 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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
For the time being, these tests will ignore the flood of deprecated
yield test warnings. Fixing those is for another PR.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
See https://github.com/travis-ci/travis-ci/issues/8920 .
|
| |
|
|
|
|
| |
Disable "-Wsign-compare" and "-Wunused-result" gcc warnings.
These seem to have been enabled by default recently for wheels
sdist builds.
|
| |
|
|
| |
They are not worth two seperate slow test runs.
|
| |
|
|
| |
Too noise and not really worth fixing.
|
| |
|
|
| |
Except the builtin lapack job as that is mostly generated code.
|
| | |
|
| |\
| |
| | |
BLD: rewrite np.distutils.exec_command.exec_command()
|
| | |
| |
| |
| |
| |
| | |
exec_command() is currently a mess of several implementations using outdated
Python APIs and various hacks. This rewrites it to use the standard
subprocess module. See PR #7614 for previous discussion.
|
| | |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| | |
the files in doc/ and numpy/ were covered in previous commits
|
| |/ |
|
| | |
|