Simon McNamara wrote:
This java compiles and runs fine, but doesn't launch the python. No exceptions. No nothing.
Simon McNamara wrote:Jython is not an option for me.
SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6 - OCEJPAD 6
How To Ask Questions How To Answer Questions
Simon McNamara wrote:
For the life of me I cannot get my PyQt4 problem resolved.
Simon McNamara wrote:
The shipped version of python for MacOS is 2.7.x .
Simon McNamara wrote:GNURadio simply requires PyQt4 (I received the same error). I would not be surprised if GNURadio requires the older module PyQt4.
Simon McNamara wrote:
How would I find the correct path for python3? The path to python2.7 seems totally different (e.g., something like /usr/lib/python2.7).
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Clarification Update January 8, 2020
Effective January 1, 2020, no new bug reports, fixes, or changes will be made to Python 2.
After Python 2.7.17 (October 19, 2019) was released, some additional changes accumulated before the end of 2019 when the core development team froze the 2.7 branch. As a final service to the community, python-dev will bundle those fixes -- and only those fixes -- into a final 2.7.18 release. The release date for 2.7.18 will be in April 2020 because that allows time for the release managers to complete a release candidate and final release.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
A bigger question however is whether the python part is even needed here. Gnuradio itself is a self-contained engine, and while it has a Python API to allow certain functions, I think you might be able to run a canned flow without it.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
If you're going to use Runtime.exec() or one of the other external program execution resources, then you should actually use the absolute program path. That is "/usr/bin/python", not just "python". Don't depend on the JVM's shell path. You may also need to intercept the stdio paths for the python interpreter.
If you just want to run a preset gnuradio from Java, that's probably it...
It seems that the gr-gsm-0.41.2-1 package is incompatible with gnuradio-3.7.11-6 and there is no easy way to fix it. The gnuradio package in Debian Buster has been heavily modified and all distributions that are directly or indirectly based on Debian Buster are affected - Ubuntu 18.04, Kali Rolling, Parrot Os, .... This error is not because of missing qt library but because of incompatibility between grgsm_livemon and the latest gnuradio versions from Debian/Ubuntu/Kali repositories. The gnuradio in debian has been migrated from qt4 to qt5 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874893) so all QT flowgraphs have to be regenerated.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.