mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-26 04:05:49 +03:00
[GH-ISSUE #210] ImportError #190
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 @madtatu-development on GitHub (Nov 4, 2021).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/210
Background:
after I couldnt create the EXE after updating to Python 3.10,0, I had decided to go back to 3.9.7
since I am using ssd image base backup, I simply restored an earlier OS image where python wasnt installed at all to ensure there is no garbage left e.g. from an uninstall proces.
I installed python 3.9.7 x64 on windows 10 latest version, just as it was before.
Problem:
for some reason, the EXACT SAME code with the EXACT same json settings file, which was perfectly compiled to exe and executed earlier, now, throws the following error during execution:
ImportError: Module 'pythoncom' isn't in frozen sys.path ['C:\Users\Master\AppData\Local\Temp_MEI47642\base_library.zip', 'C:\Users\Master\AppData\Local\Temp_MEI47642\lib-dynload', 'C:\Users\Master\AppData\Local\Temp_MEI47642']
All required dirs are added.
All modules and submodules are imported.
Cache emptied.
Both python and python/scripts added to os syst path variable
Still not work. what previously worked like a charm.
I am sure the problem is on my side, eventhough it is same evironment, code and process, but there is no miracle, something must had been changed what i overlook otherwise it would not give an error.
May I ask if you could guide me, what he heck could be the problem ?
@brentvollebregt commented on GitHub (Nov 4, 2021):
This may be an issue with mixed architectures for pywin32 and Python as hinted here. I would recommend reinstalling pywin32 through pip and seeing if that helps.
@github-actions[bot] commented on GitHub (Jan 4, 2022):
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.
@github-actions[bot] commented on GitHub (Jan 9, 2022):
Closing issue due to no activity in more than 60 days.