| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Josh Morman <jmorman@gnuradio.org>
|
| |
|
|
|
|
| |
Contributed by Marcus Leech
Signed-off-by: Jeff Long <willcode4@gmail.com>
|
| |
|
|
|
|
|
| |
Block would fail as soon as it was placed in GRC.
A couple of imports/renames were needed.
Signed-off-by: Jeff Long <willcode4@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All of the removed `from __future__ import` were needed in older
versions of Python (mostly 2.5.x and below) but later became mandatory
in most versions of Python 3 hence are not necessary anymore.
More specifically, according to __future__.py[1]:
- unicode_literals is part of Python since versions 2.6.0 and 3.0.0;
- print_function is part of Python since versions 2.6.0 and 3.0.0;
- absolute_import is part of Python since versions 2.5.0 and 3.0.0;
- division is part of Python since versions 2.2.0 and 3.0.0;
Get rid of those unnecessary imports to slightly clean up the codebase.
[1] https://github.com/python/cpython/blob/master/Lib/__future__.py
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
gr-fft/python/fft/logpwrfft.py
|
| | |
| |
| |
| |
| |
| | |
That is especially hurt as the GRC template puts defaults to
`ref_scale=2` (int literal!) and if someone uses `1`, they'll get zero
internally in logpwrfft, and that leads to errors.
|
| |/ |
|
| |
|
|
| |
We should be more careful about letting these into the code in the future. In emacs, we can use (add-hook 'before-save-hook 'delete-trailing-whitespace).
|
| |
|
|
| |
(fixes issue #609 reported by Sylvain Munaut).
|
| |
|
