mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-25 11:45:49 +03:00
[GH-ISSUE #441] time.sleep() is not working correctly #349
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 @revolexGeek on GitHub (Nov 8, 2023).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/441
Quick Checks
Describe the bug
When running an application through a Python file (.py), the time.sleep(x) command works fine, but after compiling through auto-py-to-exe, it happens that no time.sleep(x) is triggered and the program runs straight through without the necessary stops.
To Reproduce
Steps to reproduce the behavior (install dependencies, do this in the auto-py-to-exe UI):
0. Run python code via
python main.pyand see that everything works fine!1.1. Select
One File1.2. Select
Console Based1.3. Select some icon
1.4. Give it some name in
Advancedcategory1.5. Compile (convert) it.
A minimal reproducible example:
Live representation of error

Expected behavior
Delays had to be triggered so that the functioning of the converted program was identical to that of the unconverted program.
Your Environment:
python --version): 3.9.0pip show auto-py-to-exe): 2.42.0pip show pyinstaller): 6.1.0pip show eel): 0.16.0@github-actions[bot] commented on GitHub (Nov 8, 2023):
👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section.
Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion.
@brentvollebregt commented on GitHub (Nov 8, 2023):
I've just tried to reproduce this with the following,
Unfortunately, this didn't happen for me - do you know if this only happens on Python 3.9.0?
@revolexGeek commented on GitHub (Nov 8, 2023):
I recently changed Python version from 3.8.0 to 3.9.0, while on 3.8.0 everything was great with auto-py-to-exe, but on 3.9.0 suddenly this happens 🤷
@brentvollebregt commented on GitHub (Nov 9, 2023):
Have you tried any other versions of Python above 3.9.0? Did any of those work?
Also if you run
pyinstaller --noconfirm --onefile --console "path/to/file.py"(using PyInstaller from your Python 3.9.0 environment) and then run the output exe, does this also have the same issue?@MothScientist commented on GitHub (Nov 10, 2023):
Checked on 2 versions:
1:
The problem is not observed.
2:
The problem repeats itself, as stated in the description.
@MothScientist commented on GitHub (Nov 10, 2023):
I ran it like this:
pyinstaller --noconfirm --onefile --console "path/to/file.py"- the problem repeats, no changes (version 3.9.0)@brentvollebregt commented on GitHub (Nov 13, 2023):
Thanks for running those, sorry for the late reply. The fact that this still happens when running
pyinstaller ...shows the issue is with PyInstaller and not anything specific to auto-py-to-exe.Unfortunately, there is nothing I can do about this in auto-py-to-exe. Still, you could raise it as a PyInstaller issue - your demo (code and gif) is excellent and the simple
pyinstaller --noconfirm --onefile --console "path/to/file.py"command would be ideal to note in the issue as well as your PyInstaller and Python versions.@MothScientist commented on GitHub (Nov 14, 2023):
Ok, I opened issue in the pyinstaller repository: https://github.com/pyinstaller/pyinstaller/issues/8104.
If something is wrong or forgot to add something, then please write a comment to issue.
@brentvollebregt commented on GitHub (Nov 14, 2023):
Looks excellent!