| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
closes #8444
|
|
|
|
|
|
|
|
|
| |
Corrections to #7492.
Correct the examples in the notes specifying the output length for the
hfft. Also clean up the documentation a bit.
[ci skip]
|
| |
|
|
|
|
|
|
| |
There is now a lock around cache accesses ensuring thread safety. The
size of a cache entry is now also calculated by summing over all arrays
in the list.
|
|
|
|
|
|
|
|
| |
Replaces the simple dictionary caches for the twiddle factors of
numpy.fft to bounded LRU (least recently used) caches. The caches can
thus no longer grow without bounds.
See #7686.
|
| |
|
|
|
|
| |
Closes #6693
|
| |
|
|
|
|
|
| |
The relationship between frequency and position in the input array
is clarified.
|
| |
|
|
|
|
|
| |
Numpy will no longer support the bento build system, so remove the
associated files.
|
|
|
|
| |
Not sure why the error was still in the docs.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This is because of the inclusion of numpy/ndarraytypes.h in b3121e8.
|
| |
|
|\
| |
| |
| | |
PyErr_NoMemory when PyArray_Zeros fails to initialize
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Resolves issue #565.
The public fft functions defined in fftpack.c have name conflicts on certain
systems, so the prefix "npy_" was added to these functions.
Added NPY_VISIBILITY_HIDDEN to the public functions in both fftpack.h and
fftpack.c. This required rearranging the includes at the beginning of
fftpack_litemodule.c so that this macro was properly defined. In addition,
Python.h and numpy/ndarraytypes.h were included in the fftpack.h.
One function, rfftb1, was flagged as `static` as it was not exported in the
header.
Build and tests pass using both Python 2.7.8 and Python 3.4.2.
|
|\ \
| | |
| | | |
MAINT: fft: cleanup in fftpack module
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* put string constants in const arrays
* use static functions were possible
* removed a stale comment
* more consistent whitespace
|
|\ \ \
| |/ /
|/| | |
TST: join fft threads before getting values
|
| |/
| |
| |
| | |
avoids timeouts on slow machines
|
|/ |
|
|\
| |
| | |
BUG: fix crash when sending interrupt signal to fft functions
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the SIGINT handling code must be in the GIL released section so the
longjmp does not skip the retaking.
This implies that the signal handlers must use thread local storage to
avoid a crash when sending interrupt to threaded fft functions.
Distribution of SIGINT to each threads must be handled by the
application as only the master thread receives it
Closes gh-4634
|
| |
| |
| |
| |
| |
| | |
Fixes issue #4736
The example showed a call to np.fft.fft instead of np.fft.fft2.
|
|/
|
|
|
| |
tests should not use more than 500 MB of memory, this one uses more than
a GB. Also it didn't join its threads.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
On Python 2.7, the long type was excluded.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
outputs
|
|
|
| |
Says Hermite spectrum when it means signal
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Now is as good a time as any with open PR's at a low.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Python 3 removes the builtin types from the types module. The types
fixer replaces such references with the builtin types where possible
and also takes care of some special cases:
types.TypeNone <- type(None)
types.NotImplementedType <- type(NotImplemented)
types.EllipsisType <- type(Ellipsis)
The only two tricky substitutions are
types.StringType <- bytes
types.LongType <- int
These are fixed up to support both Python 3 and Python 2 code by
importing the long and bytes types from numpy.compat.
Closes #3240.
|
|
|
|
|
|
|
| |
Add `print_function` to all `from __future__ import ...` statements
and use the python3 print function syntax everywhere.
Closes #3078.
|
|\
| |
| | |
2to3 apply import fixer
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|