| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Complete Cache will be discarded if current cache file
* has no version info
* version older than version in cacheversion.in (i.e. after an update)
Cached entry will be reloaded from yaml if
* missing
* cached-at property smaller than modification time of yaml file (half
second tolerance, due to inelegant floating point modification time
handling in python)
Also, a bit of debug logging.
Signed-off-by: Marcus Müller <mmueller@gnuradio.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
This raises an RuntimeError describing that GRC could not find the
built-in blocks rather than raising a KeyError on "options", which
left users with little to go on. This error has come up in various
situations involving an incorrect blocks path (due to mixing GR
versions causing the configuration files to point to the wrong
installation) or simply the blocks not being installed.
Signed-off-by: Ryan Volz <ryan.volz@gmail.com>
|
| |
|
|
|
|
|
|
|
|
| |
This is an update for PR #2424. The extra debug output from GRC was
being generated by another logger instance in grc/core/platform that
did not respect the command line arguments.
This removes the extra logger and sets the logger level in main to
whatever is requested from the command line. See grc/main.py:43 for more
detail.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
add method to the Messages module to print flowgraph
errors in a verbose format
|
| |
|
|
|
|
| |
Wrote function in Platform to use get_error_messages()
member function from parent class and report these upon
a flowgraph loading exception.
|
| |
|
|
|
|
| |
Moves the yaml file load inside the try block
Fixes #2668
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
If a hier2 block contains more than one ( input or output ) message port
GRC generates a wrong yml description of this block.
If you restart GRC, GRC terminates with an error messages is no longer usable.
This can be verified with the example here: "gr-blocks/examples/msg_passing/hier"
This example is running in 3.7 without any problems.
The modification in platform.py avoids the termination of grc
if there is an error in the flowgraph to be loaded.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|
|
Includes basic converter from XML/Cheetah to YAML/Mako based block format.
|
