| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
Fixes gh-16354. Previously np.poly1d(z).coeffs.dtype would always
be np.float64 for zero array z, regardless of z's dtype.
|
| |
|
| |
Fix bug caused by typo and added tests
|
| |
|
|
|
|
|
| |
Inheriting from object was necessary for Python 2 compatibility to use
new-style classes. In Python 3, this is unnecessary as there are no
old-style classes.
Dropping the object is more idiomatic Python.
|
| |
|
|
|
| |
As numpy is Python 3 only, these import statements are now unnecessary
and don't alter runtime behavior.
|
| |\ |
|
| | |
| |
| |
| | |
disable scaling completely.
|
| | |
| |
| |
| | |
regular tests. (#GH9416).
|
| | | |
|
| | |
| |
| |
| |
| | |
That function is nose specific and has not worked since `__init__` files
were added to the tests directories.
|
| | |
| |
| |
| |
| |
| | |
This previously failed with:
TypeError: Cannot cast ufunc subtract output from dtype('complex128') to dtype('float64') with casting rule 'same_kind'
|
| | | |
|
| |/
|
|
|
|
|
| |
Turns out that this was relied upon downstream
We also add a setter for coeffs, so that augmented assignment does not both
change state and raise an exception suggesting state could not be changed.
|
| |
|
|
| |
Remove the comment suggesting that they are not
|
| |
|
|
| |
Fixes #8760
|
| |
|
|
| |
Also a slight refactoring of np.polyfit.
|
| |
|
|
| |
also fixed some PEP8 issues
|
| |
|
|
| |
Change to a deterministic test instead of using rand
|
| | |
|
| |
|
|
|
|
| |
Closes #5096. Casts integer arrays to np.double, to prevent
integer overflow. Object arrays are left unchanged, to allow
use of arbitrary precision objects.
|
| |
|
|
|
|
|
| |
The possibly controversial part of this is making the nested array
value lists PEP8 compliant, as there is something to be said aligning
the values for clarity. In the end, it seemed like the easiest thing
to do was to make them PEP8 compliant. The eye can get used to that.
|
| | |
|
| |
|
|
|
|
|
| |
Run autopep8 over the test files in numpy/lib/test and make fixes
to the result.
Also remove Python5 workaround.
|
| |
|
|
|
|
|
| |
Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long
and will need to be broken at some point. OTOH, some lines were already
too long and need to be broken at some point. Now seems as good a time
as any to do this with open PRs at a minimum.
|
| |
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new import `absolute_import` is added the `from __future__ import`
statement and The 2to3 `import` fixer is run to make the imports
compatible. There are several things that need to be dealt with to make
this work.
1) Files meant to be run as scripts run in a different environment than
files imported as part of a package, and so changes to those files need
to be skipped. The affected script files are:
* all setup.py files
* numpy/core/code_generators/generate_umath.py
* numpy/core/code_generators/generate_numpy_api.py
* numpy/core/code_generators/generate_ufunc_api.py
2) Some imported modules are not available as they are created during
the build process and consequently 2to3 is unable to handle them
correctly. Files that import those modules need a bit of extra work.
The affected files are:
* core/__init__.py,
* core/numeric.py,
* core/_internal.py,
* core/arrayprint.py,
* core/fromnumeric.py,
* numpy/__init__.py,
* lib/npyio.py,
* lib/function_base.py,
* fft/fftpack.py,
* random/__init__.py
Closes #3172
|
| |
|
|
|
|
|
|
| |
This should be harmless, as we already are division clean. However,
placement of this import takes some care. In the future a script
can be used to append new features without worry, at least until
such time as it exceeds a single line. Having that ability will
make it easier to deal with absolute imports and printing updates.
|
| | |
|
| | |
|
| |
|
|
| |
assert in non-testing files that should be checked for correctness.
|
| | |
|
| |
|
|
|
|
|
| |
The failure only occurs on Windows and Python 2.5, there the printing of
floating point numbers is slightly different. Since this is a doctest and can
not be marked conditionally as knownfail, just removing it is simplest. It's
not a bug anyway.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Added numpy.testing.run_module_suite to simplify "if __name__ == '__main__'" boilerplate code in test
modules.
Removed numpy/testing/pkgtester.py since it just consisted of an import statement after porting SciPy r4424.
Allow numpy.*.test() to accept the old keyword arguments (but issue a deprecation warning when old arguments
are seen).
numpy.*.test() returns a test result object as before.
Fixed typo in distutils doc.
|
| |
|
|
| |
modules.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
zero. Closes ticket #564.
|
| | |
|
| |
|
|
| |
elements in object arrays.
|
| | |
|
| |
|
|
| |
machinery - needed for running tests via testoob.
|
| | |
|
| |
|
|
| |
.dtypechar -> .dtype.char
|
| | |
|
