| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Josh Morman <jmorman@gnuradio.org>
|
| |
|
|
| |
Signed-off-by: Håkon Vågsether <hauk142@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
At the moment grc does not validate variables, as they are of type raw.
So they are always treated as valid, which leads to some problems, see: #4519.
A approach to fix #4519 is #4531.
This approach improves the situation, but has still some problems.
param.py provides a validator function for dtype raw, but this is not used, as dtypes.py provides no validator function for dtype raw.
This fix clears the error messages in base.rewrite not in base.elements.validate, so the error messages are kept.
In addition this makes it possible, to make the code in VariableEditor.py smoother.
The error messages are kept on switching the different tabs in VariableEditor.
Signed-off-by: Volker Schroer <3470424+dl1ksv@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some objects, notably PMTs can produce non-UTF-8 strings when
their __str__() method is called. For instance
>>> str(pmt.init_u8vector(1, [203]))
'#[\udccb]'
These kinds of strings eventually give a UnicodeEncodeError, for
instance when calling print() or displaying them with GTK. Python3
strings are supposed to be valid UTF-8.
When these objects are used inside block parameters in GRC, it will
produce several tracebacks and hang up. This commit fixes the problem
by sanitizing the strings to convert them to valid UTF-8. The sanitization
uses the 'backslashreplace' error response from Python.
Issue #3398 is caused by this problem.
Signed-off-by: Martin Braun <martin@gnuradio.org>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
Variable blocks must not have a param named value. But grc always trys to evaluate this params.
This leads to errors
|
| |
|
|
| |
useful for variable and parameter blocks, but maybe others too
|
| | |
|
| | |
|
| |
|
|
| |
Includes basic converter from XML/Cheetah to YAML/Mako based block format.
|
| | |
|
| |\ |
|
| | |\ |
|
| | | | |
|
| | |/ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
