mirror of
https://github.com/freedomofpress/dangerzone.git
synced 2025-04-28 18:02:38 +02:00
418b68d4ca
This is a common pitfall of pyinstaller, when using multiprocessing. In our case, the spawned processes is passed the -B option, thinking it's python (but it's dangerzone). > -B Don't write .pyc files on import. See also PYTHONDONTWRITEBYTECODE. As a result, dangerzone is spawned with the -B option, which doesn't mean anything for it. > In the frozen application, sys.executable points to your application > executable. So when the multiprocessing module in your main process > attempts to spawn a subprocess (a worker or the resource tracker), it > runs another instance of your program, with the following arguments for > resource tracker: > > my_program -B -S -I -c "from multiprocessing.resource_tracker import main;main(5)" https://pyinstaller.org/en/stable/common-issues-and-pitfalls.html#multi-processing |
||
|---|---|---|
| .. | ||
| container_helpers | ||
| conversion | ||
| gui | ||
| isolation_provider | ||
| __init__.py | ||
| args.py | ||
| cli.py | ||
| container_utils.py | ||
| document.py | ||
| errors.py | ||
| logic.py | ||
| settings.py | ||
| util.py | ||