Electron打包Linux应用后Python脚本无法执行的问题求助

问题概述 #

打包Electron应用为Linux版本后，后台执行的Python脚本无法正常运行，已尝试ASAR解压配置、extraResources资源打包及路径调整，问题仍未解决。

文件夹结构 #

- App.Root
   |-public
   |    -background.html
   |
   |-scripts
        -python.py

相关代码 #

background.html核心逻辑 #

<script>
const { PythonShell } = require('python-shell');
const { ipcRenderer } = require('electron');
const path = require('path');

let pyshell

ipcRenderer.on('START_PROCESSING', (event, args) => {

    console.log("Loading Python")

    const { data } = args;
    pyshell = new PythonShell(path.join(process.resourcesPath, '/scripts/python.py'), {
        pythonPath: 'python3',
        pythonOptions:['-u'],
        args: [data]
    });

    pyshell.on('message', function (results) {
        ipcRenderer.send('MESSAGE_FROM_BACKGROUND', { message: results });
    });

});

ipcRenderer.on('QUIT_PYTHON', (event, args) => {
    pyshell.kill();
    ipcRenderer.send('CLOSE_BACKGROUND');
});

ipcRenderer.send('BACKGROUND_READY');
</script>

当前Build配置 #

"build": {
  "files": [
    "build/**/*",
    "node_modules/**/*"
  ],
  "asarUnpack":"./scripts/**",
  "extraResources": "./scripts/**",

  "publish": {
    "provider": "github",
    "repo": "test",
    "owner": "Test"
  }
},

解决方案 #

1. 清理冗余的Build配置项 #

同时设置asarUnpack和extraResources会导致scripts文件夹重复打包，保留extraResources即可（Python脚本无需打包进asar包），修改后配置如下：

"build": {
  "files": [
    "build/**/*",
    "node_modules/**/*"
  ],
  "extraResources": [
    {
      "from": "./scripts/",
      "to": "./scripts/"
    }
  ],
  "publish": {
    "provider": "github",
    "repo": "test",
    "owner": "Test"
  }
}

2. 修正Python执行路径 #

Linux环境中python3可能不在默认PATH或存在权限问题，直接指定绝对路径更可靠：

pyshell = new PythonShell(path.join(process.resourcesPath, '/scripts/python.py'), {
    pythonPath: '/usr/bin/python3', // 可用终端命令`which python3`获取实际路径
    pythonOptions:['-u'],
    args: [data]
});

3. 确保Python脚本有执行权限 #

打包前给脚本添加执行权限，或在配置中指定权限：

• 终端手动设置权限：

chmod +x ./scripts/python.py

• 或在extraResources中配置权限：

"extraResources": [
  {
    "from": "./scripts/",
    "to": "./scripts/",
    "filter": ["**/*.py"],
    "mode": 0o755
  }
]

4. 调试路径有效性 #

在background.html中添加日志，确认脚本路径是否正确：

const scriptPath = path.join(process.resourcesPath, '/scripts/python.py');
console.log('Python脚本路径:', scriptPath);

// 检查文件是否存在
const fs = require('fs');
if (fs.existsSync(scriptPath)) {
    console.log('脚本存在');
} else {
    console.log('脚本不存在');
}

打包后在终端运行应用查看日志：

./你的应用名 --enable-logging

5. 检查Python依赖 #

确保目标Linux机器已安装脚本所需的所有第三方依赖，或用pyinstaller将Python脚本打包成独立可执行文件，避免环境依赖问题。

内容的提问来源于stack exchange，提问作者Traxan