在子进程中运行 Pyinstaller 单个可执行输出时无法重定向它

Cannot redirect Pyinstaller single executable output while running it in subprocess(在子进程中运行 Pyinstaller 单个可执行输出时无法重定向它)

问题描述

我已经为此苦苦挣扎了一段时间.我已经设法编写了一个可以捕获 .py 文件的 STDOUT 的代码，但是当我使用从 Pyinstaller 生成的可执行文件运行完全相同的代码时(不管它是否窗口化)readyReadStandardOutput 信号永远不会出现.

I've been struggling with this for quite a while. I've managed to write a code that can capture STDOUT of .py files, however when I run the exact same code with executable generated from Pyinstaller (doesn't matter whether it's windowed or not) the readyReadStandardOutput signal doesn't ever come up.

根据我的测试，只有在应用程序崩溃时才会发出任何信号，但是我需要 GUI 和可执行文件之间的实时通信.

From my tests it occurs that any signal at all is emitted only when the app crashes, however I need a live communication between the GUI and the executable.

这是我的参考代码:

  def start_process(self, program, args=None):
        if args is None:
            args = []

        process = QtCore.QProcess(self)
        process.readyReadStandardOutput.connect(partial(self.onReadyReadStandardOutput, self.number_process_running))

        process.start(program)

以及我将信号连接到的方法:

and the method that I've connected the signal to:

    def onReadyReadStandardOutput(self, i):
        print("called")
        process = self.sender()
        self.results[i] = process.readAllStandardOutput()
        self.resultsChanged.emit(self.results)

我正在使用 Windows 机器

I'm working on a Windows machine

最小的可重现示例

我们来写一个小脚本

import time

if __name__ == "__main__":
    num = 0
    while True:
        num = num + 1
        print(num)
        time.sleep(3)

让我们暂时离开 PyQT 进程并使用更简单的 Popen.如果我们在 Popen 中运行脚本，stdout 将被重定向到调用进程.

Let's leave the PyQT processes for now and use simpler Popen. If we run the script in Popen, the stdout will be redirected to the calling process.

if __name__ == '__main__':
    p = Popen([r'python', 'test.py'], stdin=PIPE, stdout=PIPE, stderr=PIPE)
    while p.poll() is None:
        out = p.stdout.readline()
        print(out)

但是，如果我们使用第一个脚本并通过 PyInstaller 单个可执行文件生成器，Popen 将不再捕获任何输出，它只会冻结

However, if we take the first script and put through PyInstaller single executable generator, the Popen won't capture any output no more, it will just freeze

import os
import sys

import PyInstaller.__main__

file_location = os.path.dirname(os.path.realpath(__file__))

if sys.platform == "win32":
    PyInstaller.__main__.run([
        '--name=%s' % 'test',
        '--onefile',
        '--noconsole',
        '--distpath=%s' % os.path.join(file_location, 'dist'),
        '--workpath=%s' % os.path.join(file_location, 'build'),
        '--specpath=%s' % os.path.join(file_location),
        os.path.join(file_location, 'test.py'),
    ])

所以我的问题是 - 我错过了其中的一些重要部分吗?或者也许这只是 pyinstaller 的错.

So again my question is - am I missing some important part in there? Or maybe it's just pyinstaller's fault.

推荐答案

看来你在编译脚本的时候应该把print的flush设置为True，所以改成:

It seems that when you compile the script you should set the flush of the print to True, so just change it to:

import time

if __name__ == "__main__":
    num = 0
    while True:
        num = num + 1
        print(num, flush=True)
        time.sleep(3)

这篇关于在子进程中运行 Pyinstaller 单个可执行输出时无法重定向它的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！