Here’s a trick question…
I followed your tutorial about using Qprocess to launch an external script/program. This allows me to start the program FROM a pyqt application and monitor and get results from it…but what if I need to connect to an exterbal program that is ALREADY running in the background 24/7 ? Is there a way to code that program so that it is outputting stuff all the time…and then when i connect with a pyqt gui it gives me a view on it? Thanks.
i guess this is not possible?
someone with experience with this could you please write a “yes” or “no”? or direct me to a place to find out more? thank you!
Hi @mrwonderfulness11014 welcome to the forum!
Which platform is your process running on, and how is it started? Do you have control over the launching of the background process?
The easiest way is to redirect output to a file when starting up your long running process. If you only want to get results from it then this would be enough.
On Linux if you start a process using screen you can attach/detach it will – it should be possible to launch screen from within a QProcess and from there communicate as normal. Alternatively, if you know the pid of the running process you can also (with the same user) read from the pseudo-files at /proc/<pid>/fd (0 stdin, 1 stdout, 2 stderr). Lastly, you can connect to a running processing using gdb.
Hi Martin,
thank you for your reply. yes, after googling around and looking at qt docs this seems to be the case. for working with python, what would you say the most performant file reading setup could be? i’ll have quite a bit of data. perhaps something like redis or other in memory db, sqlite, etc. i’ll run some tests but i’m wondering if there is a best practices way of doing this with python and qt. best regards.
It’s difficult to give a definitive answer without seeing the data. If you need to read the data repeatedly, in parts or lookup specific elements then sqlite or a database (in memory/on disk) would be better than files. But if you’re just loading different datasets and can’t prepare a database/memory store in advance, files would be the better option.
Qt doesn’t really mind how you have the data stored. If you’re using the model views you’ll need to implement an interface (and some kind of caching) since the views require a lot of data lookups for individual cells (usually very inefficient to hit a database for that).
If you’re passing data in/out of a process then an external data store then you have a choice between piping the data or using an external data store (including a a file). Pipes make more sense when streaming the data (i.e. you have a live output) and don’t need to store the result. If you’re storing the data and only need access to the finished result, I’d put it in a store/file and just notify the main process to read it once you’re done.
Does that make sense? If you have more details of the data I’m happy to go into it further.
here is an example with tmux i found helpful way back.
what martin mentioned about writing to a file and then using something like this would be one way depending on the app and how its outputting information.