| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
This test was reported to be failing once for 1.6.2rc1, test precision may be
set slightly too agressive.
|
| |
|
|
|
|
|
|
|
| |
The --cover-inclusive argument means that coverage.py tries to include every
single .py file in the source tree in the coverage report. This leads to test
errors, because it tries to import files like setupscons.py (which will of
course directly fail for anyone not having numscons installed).
(backport of bfaaefe5)
|
| | |
|
| |\
| |
| | |
Backport numpy.random fix for MSVC.
|
| | |
| |
| |
| |
| |
| |
| | |
This fixes a problem on 64 bit Windows where a 64 bit index is
needed but long is only 32 bits.
Regenerate mtrand.c
|
| |\ \
| | |
| | | |
Backport numpy.poly bug fixes and documentation improvements.
|
| | | |
| | |
| | |
| | | |
Use divmod instead of // and % separately.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The original method was overly sensitive to roundoff. Of the two
approaches considered, gauss integration or binary subdivision of
the roots, the latter is more compatible with using other number
representations such as mpmath. No method is going to be suitable
for large numbers of arbitrary zeros but the current method is a
significant improvement.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In particular for arithmetic where one could end up with a Polynomial
type with Chebyshev coefficients after an addition. It is unlikely that
that would be done on purpose.
The PolyDomain error message was also replaced by a TypeError with
an appropriate message. That seems like a better choice.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This is the first step in cleaning up the polynomial documentation
and writing an instructional section on the convenience classes.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The new companion matrices are related to the old by a
similarity transformation that makes them better conditioned
for root finding. In particular, the companion matrices for
the orthogonal polynomials are symmetric when the zeros of a
single polynomial term is wanted. This produces better zeros
for use in Gauss quadrature.
|
| | |/ |
|
| |\ \
| | |
| | | |
Backport f2py fixes and improvements.
|
| | | |
| | |
| | |
| | |
| | | |
Newer Fortran compilers for Intel may support quad precision, so
_selected_real_kind_func needs to report that for precisions >= 19.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add new options extra_f77_compile_args and extra_f90_compile_args to
Configuration.add_extension. Configuration.add_library, and Extension.
These options allow specifying extra compile options for compiling Fortran
sources within a setup.py file.
|
| | | |
| | |
| | |
| | |
| | | |
follow build_ext coding convention in build_clib to catch strange fcompiler
value reported in ml.
|
| | |/
| |
| |
| |
| |
| |
| | |
Introduce new options extra_f77_compiler_args and extra_f90_compiler_args
to Configuration.add_extension. Configuration.add_library, and Extension.
These options allow specifying extra compile options for compiling Fortran
sources within a setup.py file.
|
| |\ \
| | |
| | | |
Backport numpy.lib bug fixes.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is caused by the inconsistent floating point handling of Python itself.
On Windows with 2.5:
>>> "%s" % 1e-6
'1e-006'
With 2.6:
>>> "%s" % 1e-6
'1e-06'
Reviewed as PR-225.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This should fix:
* http://projects.scipy.org/numpy/ticket/1848
* http://projects.scipy.org/scipy/ticket/1449
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| | |
This allows these objects to be freed by refcount, rather than requiring
the gc, which can be useful in some situations.
|
| |\ \
| | |
| | |
| | |
| | | |
Backport numpy.core bug fixes.
All tested on MSVC, OS X and with a full release build on Windows.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Should be using npy_intp rather than int.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Squashed backport also containing two following commits.
TST: Test float16 __array_interface__.
STY: Cleanup test_half.py a bit.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The return from PyArray_DescrFromObject PyArray_SearchSorted needed
to be checked for NULL. Also added checks in other spots where
PyArray_DescrFromObject was called. Added regression test for same.
Made a few small code cleanups along the way.
All the checks may not be necessary, but
1) No one should have to waste brain cycles figuring that out.
2) Bugs happen.
3) Things change.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Attempted attribute deletion raises an Attribute error. Deleting
an iterator index or slice raises a TypeError. This is a change for
nditer, which used to raise ValueError when deletes were attempted.
|
| | | |
| | |
| | |
| | |
| | | |
Add check for NULL in setter functions and return Attribute error
if found.
|
| | | |
| | |
| | |
| | | |
Backport of PR #207.
|
| | | |
| | |
| | |
| | | |
Also return nan for resulting non-positive degrees of freedom.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a squashed backport of 4 commits.
STY: cleanup hashdesc.c to follow our C conventions.
BUG: fix inconsistencies in dtype flag type at the C level.
Conflicts:
numpy/core/src/multiarray/descriptor.c
numpy/core/src/multiarray/hashdescr.c
BUG: fix #2017 by ignoring type_num in the hash input.
Since type_num is not considered in PyArray_EquivTypes (for dtype
equality comparison), seems reasonable to ignore it for hashing as
well.
Conflicts:
numpy/core/tests/test_dtype.py
BUG: fix flags type when exposed to python.
|
| | | |
| | |
| | |
| | |
| | | |
The consequence of this bug was the __rdivmod__ wasn't called for user
classes that defined __array_priority__.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
Also clean up the logic behind handling infs.
Squashed backport of 3503c5f..aea76b8.
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Backport of 88e8c15.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Backport of 7497d60.
Also actually runs tests. Tests were not run before because the allclose
test class was a subclass of TestCase and used generators. This is not
supported by nose, tests will be skipped.
Also changes plain asserts to assert_().
Thanks to Justin Peel for the allclose inf fix.
|
| | | |
| | |
| | |
| | | |
concatenate.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is a backport of 4daf949
PyArray_FromBuffer: Allow creating arrays from empty buffers
or empty slices.
That finally closed the ticket.
|