summaryrefslogtreecommitdiff
path: root/numpy/fft/setup.py
Commit message (Collapse)AuthorAgeFilesLines
* BUG: Fixed an issue where `.pyi` weren't picked up by numpy sub-packagesBas van Beek2020-11-031-0/+1
|
* Mark tests as a subpackage rather than data.Hameer Abbasi2020-05-061-1/+1
|
* BUG: Add _LARGE_FILES to def_macros[] when platform is AIX (gh-15938)Michael Felt2020-04-221-1/+5
| | | AIX needs to be told to use large file support at all times. Fixes parts of gh-15801.
* MAINT: Remove unnecessary 'from __future__ import ...' statementsJon Dufresne2020-01-031-2/+0
| | | | | As numpy is Python 3 only, these import statements are now unnecessary and don't alter runtime behavior.
* MAINT: move pocketfft .py/.so to `_pocketfft`Ralf Gommers2019-09-071-2/+2
| | | | These aren't public, and should have been added with underscores.
* replace fftpack with pocketfftMartin Reinecke2018-12-251-3/+3
|
* STY: minor PEP8 fixups for numpy/fft.Charles Harris2014-07-311-1/+0
|
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-1/+1
| | | | | | | 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.
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+1
| | | | | | | | 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.
* Clean up setup() calls.Pearu Peterson2007-05-111-1/+1
|
* clean up unused imports and bad whitespaceTim Leslie2007-01-091-1/+0
|
* Many name-changes in oldnumeric. This may break some numpy code that was ↵Travis Oliphant2006-08-041-0/+20
using the oldnumeric interface.