| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Also silences a spurious warning during tests (the multiplication
could give a warning).
|
|
|
|
|
|
| |
Making the outer context manager a suppress warnings gives good
control to print warnings only once in release mode and suppress
some specific warnings which cannot be easily avoided otherwise.
|
|
|
|
|
|
|
|
| |
In some places, just remove aparently unnecessary filters.
After this, all cases of ignore filters should be removed from
the tests, making testing (even multiple runs) normally fully
predictable.
|
|
|
|
|
|
| |
Comment mentions a speedup, but it seems unsure why it should
be there. Instead use an error state in divide_by_count.
Some extra complex warnings had to be ignored (but those seemed correct)
|
| |
|
|
|
|
|
|
|
|
|
| |
Printing of datetime arrays used to cause warning due to
comparison warnings in NaT. This is circumvented by using views
to integer values. Part of this should be simplified when
the deprecation is over.
Also fixes a bug with non-native byteorder.
|
|
|
|
|
|
|
| |
This means that warnings of different origin then the one tested for
behave normally. If the normal behaviour is to igonre them this might
decrease specificity in rare cases. In most cases the specificity
will be slightly higher.
|
|
|
|
|
| |
Also modify the corresponding test to suppress the non Deprecation
warnings created to test specificity.
|
|\
| |
| | |
Rebase 7763, ENH: Add new warning suppression/filtering context
|
| | |
|
| |
| |
| |
| |
| |
| | |
This context has a couple of advantages over the typical one, and can
ensure that warnings are cleanly filtered without side effect for
later tests.
|
|\ \
| | |
| | | |
BUG: Fixed masked array behavior for scalar inputs to np.ma.atleast_*d
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Docstring listed extra_f77_compiler_args and extra_f90_compiler_args
as allowed keywords, but per command/build_clib.py, lines 193-194
the recognized keywords are in fact extra_f77_compile_args and
extra_f90_compile_args.
The keyword extra_compiler_args, although non-confirmant both for
fortran keywords and to the keywords of add_extension, is consistent
with the implementation (see line 200 of build_clib.py).
|
| |/
|/|
| | |
The first dimension of the return value depends on the degree of the polynomial, not the number of elements being used in the fit.
|
|\ \
| | |
| | | |
BUG: MSVCCompiler grows 'lib' & 'include' env strings exponentially.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Each time an MSVCCompiler was instantiated the old values of
os.environ['lib'] and os.environ['include'] were concatenated to the new
values set by initializing the distutils.msvc{,9}compiler.MSVCCompiler
base class. Consequently when the the old and new values of those
variables were the same, they doubled in size with each instantiation,
leading to quickly hitting the 32,768 character limit.
|
|\ \ \
| |_|/
|/| | |
DOC: #7927. Remove deprecated note for memmap relevant for Python <2.5
|
| | | |
|
| | | |
|
| |/
|/| |
|
|\ \
| | |
| | | |
BUG: Make sure numpy globals keep identity after reload.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Reloading currently causes problems because global classes defined in
numpy/__init__.py change their identity (a is b) after reload. The
solution taken here is to move those classes to a new non-reloadable
module numpy/_globals and import them into numpy from there.
Classes moved are ModuleDeprecationWarning, VisibleDeprecationWarning,
and _NoValue.
Closes #7844.
|
|\ \ \
| | | |
| | | | |
BUG: Use keyword arguments to initialize Extension base class.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently numpy.distutils.Extension class subclasses python's
distutils.extension.Extension class and initializes the base class with
a call that uses positional arguments rather than keyword arguments.
This causes problems with setuptools 25.4.0 where the Extension class
gets a new init function that expects keyword rather than positional
arguments. We should have been using keyword arguments all along and our
luck has run out, so use proper keywords
Closes #7951.
|
|\ \ \
| |_|/
|/| | |
ENH: improve duck typing inside iscomplexobj
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Both `iscomplexobj` and `isrealobj` now try to refer to the argument's
`dtype` attribute if it exists. This significantly extends the list of
types for which `iscomplexobj` returns correct results (including e.g.
scipy sparse matrices and pandas objects).
Extended the tests of the `iscomplexobj` routine for the following cases:
* simple scalars
* standard lists (test internal auto-conversion to numpy arrays)
* "Duck typing" for objects that define a dtype attribute (either
referring to one of the existing numpy dtypes, or a custom dtype, as
pandas does)
This fixes #7924
|
|\ \ \
| |_|/
|/| | |
BUG: Guard against buggy comparisons in generic quicksort.
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Generic types may have buggy comparison operators in which case the
sentinal values in quicksort cannot be counted on to keep the pointers
from running off the ends of the array. The solution here is to
explicitly check that the pointers are in bounds when sorting generic
types.
Closes #7934.
|
|\ \
| | |
| | | |
ENH: skip or avoid gc/objectmodel differences btwn pypy and cpython
|
| | | |
|
|\ \ \
| | | |
| | | | |
BUG: Check for HAVE_LDOUBLE_DOUBLE_DOUBLE_LE in npy_math_complex.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The `_real_part_reciprocal` function is coded in two ways, one depending
on functions specific to IEEE floating point and the other using generic
code that should always work. Because PPC long double is not IEEE the
generic version should always be chosen for that architecture, but that
is currently only done when the PPC is configured as big endian. This
PR makes sure that the generic version is also chosen when the PPC is
configured as little endian.
Closes #7836.
|
| |_|/
|/| |
| | |
| | | |
[ci skip]
|
|/ /
| |
| |
| |
| |
| |
| | |
`setuptools` is now using `_msvccompile` instead of `msvccompile9`.
numpy is monkey-patching symmetrically `gen_lib_options` and `spawn` function for all compilators. But `_msvccompile.gen_lib_options` was not monkey-patched while `_msvccompile.spawn` is already monkey-patched throug the super class `ccompiler.spawn`.
This patch only symmetrically patch `_msvccompile` to prevent param file quoting.
|
|\ \
| | |
| | | |
BUG: fix for issue#7835 (ma.median of 1d)
|
| | | |
|
| |/ |
|
|/ |
|
|
|
|
| |
Closes gh-391.
|
|
|
|
| |
closes gh-7897
|
|
|
| |
Histogram documentation was missing an 'a' in the phrase 'all around performance'.
|
| |
|
|
|
|
|
|
|
| |
Structured dtypes with padding bytes fail in MaskedArrays
because of padding bytes in `dtype.descr`.
Fix is to avoid using dtype.descr.
|
| |
|
|\
| |
| | |
BUG: handle introsort depth limit properly
|
| |
| |
| |
| |
| |
| |
| | |
the larger partition needs its own depth limit else it grows faster than
logarithmic.
Also increase the stack size to hold up to 64 instead of 50 pointer
pairs else it might overflow on arrays larger than than 2^50 elements.
|
|\ \
| | |
| | | |
DOC: fix typo in documentation of loadtxt (closes #7878)
|
| |/ |
|
|\ \
| |/
|/| |
BLD: preserve library order
|