mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-26 12:15:50 +03:00
[GH-ISSUE #193] warning file already exists but should not #175
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @llluuulll on GitHub (Aug 26, 2021).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/193
Hi,
Just let you know, the probleme of Pyinstaller warning dialogues popup at start of the exe about warning file already exists but should not ... Jus reading about and it appear it is a old problem defenetly not resolved since all that years ...
This probleme hit me a soon as i have start adding pyd as additional files etc...
It seem to affect especially the --onefile build and especially the command line build without providing a spec file ... this is really sad it is exactly my setup.
This is a pure annoyance and unfortunately affect your programm to, because the generated exe using your programm have this problem witch make the use of your program useless.
The only way seem to manually modify the generated spec file to turnaround this problem, but this turnaround obligate to provide a modified spec file witch is not dynamique at all.
I know the source of the problem is not in your programm, but your programm suffer of this problem.
In case, do you have any idea of other turnaround than the one of modifying the spec file ?
Thx
@llluuulll commented on GitHub (Aug 26, 2021):
Hi,
instead of --add-data, using --ad-binary for the pyd files solve the problem.
@llluuulll commented on GitHub (Aug 26, 2021):
So,
The real cause was a unknown behaviour of auto filling of extensions list by Pyinstaller.
In my case the main script import two of all my pyd files, and this two pyd are automatically added in the extensions list, and when i was add them in the --add-data i was getting the problem about ... warning file already exists but should not ...
By using --add-binary for the pyd, Pyinstaller luckilly perform a check between the binaries and the extensions and skip the doble entry and fire an output warning for each file during the packaging.
And lastly, by just not adding at all the pyd who are imported inside the main script, all is finally ok, because the imported pyd are auto added in the extensions list and there is no need to add them anywhere else.
@brentvollebregt commented on GitHub (Aug 27, 2021):
Thank you for sharing your resolution!
@github-actions[bot] commented on GitHub (Oct 27, 2021):
This issue is stale because it has been open for 60 days with no activity. Remove stale label or comment on this issue or it will be closed in 5 days.