discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Import error using an OOT


From: Elmore Family
Subject: Re: Import error using an OOT
Date: Sun, 11 Dec 2022 12:48:09 -0500

Here is the result:
 

pi@raspberrypi:~ $ python3
Python 3.9.2 (default, Mar 12 2021, 04:06:34)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ft8
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python3.9/dist-packages/ft8/__init__.py", line 23, in <module>
    from .run_response import run_response
  File "/usr/local/lib/python3.9/dist-packages/ft8/run_response.py", line 36, in <module>
    my_call = str(parser.get('main', 'my_call_sign'))
  File "/usr/lib/python3.9/configparser.py", line 781, in get
    d = self._unify_values(section, vars)
  File "/usr/lib/python3.9/configparser.py", line 1149, in _unify_values
    raise NoSectionError(section) from None
configparser.NoSectionError: No section: 'main'

 
Jim


 
Sent: Sunday, December 11, 2022 12:15 AM
Subject: Re: Import error using an OOT
 
Type

   python3

then enter

  import ft8

and see if it works.

-- Cinaed


On 12/9/22 18:33, Elmore's wrote:
I have created an OOT which when I incorporate it in my flowgraph shows the following error:
 
Failed to evaluate import _expression_ ‘import ft8’
 
The yaml file is:
 
id: ft8_run_response
label: ft8
category: '[ft8]'
 
templates:
  imports: import ft8
  make: ft8.run_response(${ft8_button})
  callbacks:
  - set_ft8(${ft8_button})
 
#  Make one 'parameters' list entry for every parameter you want settable from the GUI.
#     Keys include:
#     * id (makes the value accessible as keyname, e.g. in the make entry)
#     * label (label shown in the GUI)
#     * dtype (e.g. int, float, complex, byte, short, xxx_vector, ...)
#     * default
parameters:
- id: ft8_button
  label: ft8_button
  dtype: raw
  default: 0
 
#  'file_format' specifies the version of the GRC yml format used in the file
#  and should usually not be changed.
file_format: 1
 
I have developed and used an OOT before without an issue. I looked at the previous OOT and reviewed the GNU Radio docs on OOTs without seeing anything different.
 
I am using Python 3.92 with GNU radio 3.9.4.0 on a Raspberry Pi.
 
I hope someone can show me the error of my ways.
 
Jim

Virus-free.www.avg.com


reply via email to

[Prev in Thread] Current Thread [Next in Thread]