This appears to be issue related to the one here:
https://stackoverflow.com/questions/36003023/json-dump-failing-with-must-be-unicode-not-str-typeerror/36003774,
and probably caused because this Win10 version is the last with py2.7
integrated.
I haven't run into this error myself, so I'm not sure why it's happening
for you.

I see three options for you:
1- Figure out what unicode characters were being used that caused python to
want to save it as unicode and don't use those (possible temp workaround)
2- Modify cache.py manually using the information on the SO link so it's
compatible.
3- Wait until I release a Python 3 version of GR 3.8 for Win10.  This is
the next task in my list, but I make no promises as to timelines.  In the
meantime, you could try 3.8.0 or 3.7.x versions.

Geof

On Tue, Aug 11, 2020 at 11:52 AM Steffen Kiel <steffenk...@outlook.dk>
wrote:

> Hello!
>
> I am trying to run the newest stable release of gnu radio on windows, and
> i am running into some issues which im not sure how to fix.
> Here is the error log when im trying to start the application:
>
> *"setting gnuradio environment*
> *WARNING:gnuradio.grc.core.platform:Slow YAML loading (libyaml not
> available)*
> *Traceback (most recent call last):*
> *  File "gnuradio-companion.py", line 102, in <module>*
> *    run_main()*
> *  File "gnuradio-companion.py", line 95, in run_main*
> *    exit(main())*
> *  File "C:\Program
> Files\GNURadio-3.8\lib\site-packages\gnuradio\grc\main.py", line 83, in
> main*
> *    platform.build_library()*
> *  File "C:\Program
> Files\GNURadio-3.8\lib\site-packages\gnuradio\grc\core\platform.py", line
> 182, in build_library*
> *    continue*
> *  File "C:\Program
> Files\GNURadio-3.8\lib\site-packages\gnuradio\grc\core\cache.py", line 89,
> in __exit__*
> *    self.save()*
> *  File "C:\Program
> Files\GNURadio-3.8\lib\site-packages\gnuradio\grc\core\cache.py", line 78,
> in save*
> *    cache_file.write(json.dumps(self.cache, ensure_ascii=False))*
> *TypeError: must be unicode, not str*
> *"*
>
> Anyone know how i can fix this error, or why im getting it in the first
> place? This is a fresh install of 3.8.1.
>
>

Reply via email to