[GH-ISSUE #28] Prompt opens for a second then closes #25

Closed
opened 2026-02-26 12:20:14 +03:00 by kerem · 5 comments
Owner

Originally created by @Franziac on GitHub (Nov 3, 2018).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/28

When I try to run run.py it just opens the prompt for a second and then closes. I don't see any errors.

Originally created by @Franziac on GitHub (Nov 3, 2018). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/28 When I try to run run.py it just opens the prompt for a second and then closes. I don't see any errors.
kerem closed this issue 2026-02-26 12:20:14 +03:00
Author
Owner

@brentvollebregt commented on GitHub (Nov 3, 2018):

Most of the time this is not an issue with auto-py-to-exe or PyInstaller but incorrect configuration (which is ok). This means you will then need to enable debugging for the project to investigate the issue and hold on to any output.

To enable debugging, go into the "Advanced" section and under the title "How to generate" put 'all' in the box beside --debug. This will print out messages to the console to help you debug.

When debugging, make sure you selected the "Console Based" button and using "One Directory" will help remove basic problems; you can switch back to "One File" when there are no more bugs and then fix the ones associated with "One File".

After re-packaging your project, open up cmd, use the cd command to change directories to where the exe is located and then execute ./my_project.exe (substitute the names). This will run the executable and any errors you were missing before will be output to the console.

<!-- gh-comment-id:435627659 --> @brentvollebregt commented on GitHub (Nov 3, 2018): Most of the time this is not an issue with auto-py-to-exe or PyInstaller but incorrect configuration (which is ok). This means you will then need to enable debugging for the project to investigate the issue and hold on to any output. To enable debugging, go into the "Advanced" section and under the title "How to generate" put 'all' in the box beside --debug. This will print out messages to the console to help you debug. When debugging, make sure you selected the "Console Based" button and using "One Directory" will help remove basic problems; you can switch back to "One File" when there are no more bugs and then fix the ones associated with "One File". After re-packaging your project, open up cmd, use the cd command to change directories to where the exe is located and then execute ./my_project.exe (substitute the names). This will run the executable and any errors you were missing before will be output to the console.
Author
Owner

@Franziac commented on GitHub (Nov 10, 2018):

I think you didn't quite understand. When I run the auto-py-to-exe.exe or
whatever the name was your program won't open on my computer just some
empty command prompt. But I got my program converted to exe with some other
program so it doesn't really matter for me. I just wanted to inform you
with this issue in case others are having it too.

Brent Vollebregt notifications@github.com kirjoitti su 4. marraskuuta
2018 klo 1.04:

Most of the time this is not an issue with auto-py-to-exe or PyInstaller
but incorrect configuration (which is ok). This means you will then need to
enable debugging for the project to investigate the issue and hold on to
any output.

To enable debugging, go into the "Advanced" section and under the title
"How to generate" put 'all' in the box beside --debug. This will print out
messages to the console to help you debug.

When debugging, make sure you selected the "Console Based" button and
using "One Directory" will help remove basic problems; you can switch back
to "One File" when there are no more bugs and then fix the ones associated
with "One File".

After re-packaging your project, open up cmd, use the cd command to change
directories to where the exe is located and then execute ./my_project.exe
(substitute the names). This will run the executable and any errors you
were missing before will be output to the console.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brentvollebregt/auto-py-to-exe/issues/28#issuecomment-435627659,
or mute the thread
https://github.com/notifications/unsubscribe-auth/An_FRDrh3uAXaDVg3rIuxh287nlKQW9Zks5uriDzgaJpZM4YMuCt
.

<!-- gh-comment-id:437628342 --> @Franziac commented on GitHub (Nov 10, 2018): I think you didn't quite understand. When I run the auto-py-to-exe.exe or whatever the name was your program won't open on my computer just some empty command prompt. But I got my program converted to exe with some other program so it doesn't really matter for me. I just wanted to inform you with this issue in case others are having it too. Brent Vollebregt <notifications@github.com> kirjoitti su 4. marraskuuta 2018 klo 1.04: > Most of the time this is not an issue with auto-py-to-exe or PyInstaller > but incorrect configuration (which is ok). This means you will then need to > enable debugging for the project to investigate the issue and hold on to > any output. > > To enable debugging, go into the "Advanced" section and under the title > "How to generate" put 'all' in the box beside --debug. This will print out > messages to the console to help you debug. > > When debugging, make sure you selected the "Console Based" button and > using "One Directory" will help remove basic problems; you can switch back > to "One File" when there are no more bugs and then fix the ones associated > with "One File". > > After re-packaging your project, open up cmd, use the cd command to change > directories to where the exe is located and then execute ./my_project.exe > (substitute the names). This will run the executable and any errors you > were missing before will be output to the console. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/brentvollebregt/auto-py-to-exe/issues/28#issuecomment-435627659>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/An_FRDrh3uAXaDVg3rIuxh287nlKQW9Zks5uriDzgaJpZM4YMuCt> > . >
Author
Owner

@brentvollebregt commented on GitHub (Nov 10, 2018):

Oh right, you mean that actuall script that runs auto-py-to-exe. If you execute it though cmd, this will preserve the output which may contain errors. These would be helpful to identify what is going on.

<!-- gh-comment-id:437631362 --> @brentvollebregt commented on GitHub (Nov 10, 2018): Oh right, you mean that actuall script that runs auto-py-to-exe. If you execute it though cmd, this will preserve the output which may contain errors. These would be helpful to identify what is going on.
Author
Owner

@Franziac commented on GitHub (Nov 11, 2018):

I'm pretty sure I didn't get any errors...

Brent Vollebregt notifications@github.com kirjoitti su 11. marraskuuta
2018 klo 1.55:

Oh right, you mean that actuall script that runs auto-py-to-exe. If you
execute it though cmd, this will preserve the output which may contain
errors. These would be helpful to identify what is going on.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brentvollebregt/auto-py-to-exe/issues/28#issuecomment-437631362,
or mute the thread
https://github.com/notifications/unsubscribe-auth/An_FRF0yzEp5wIXrlHVgonOGUEtUnm--ks5ut2dngaJpZM4YMuCt
.

<!-- gh-comment-id:437665464 --> @Franziac commented on GitHub (Nov 11, 2018): I'm pretty sure I didn't get any errors... Brent Vollebregt <notifications@github.com> kirjoitti su 11. marraskuuta 2018 klo 1.55: > Oh right, you mean that actuall script that runs auto-py-to-exe. If you > execute it though cmd, this will preserve the output which may contain > errors. These would be helpful to identify what is going on. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/brentvollebregt/auto-py-to-exe/issues/28#issuecomment-437631362>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/An_FRF0yzEp5wIXrlHVgonOGUEtUnm--ks5ut2dngaJpZM4YMuCt> > . >
Author
Owner

@brentvollebregt commented on GitHub (Nov 11, 2018):

With no information on properly reproducing this and no stack trace or individual error given, then I am going to close this issue as nothing can come out of this.

I believe that if you executed this script using something that will preserve output (like the terminal/cmd) you will find that an error is appearing. This script keeps alive from a blocking statement, thus will only stop once the blocking conditions are no longer met (managed by Eel) or an error has occurred; I believe the latter is occurring.

If you do decide to preserve the error, you can comment it and I will look at it. But as of now, this issue provides no information so I am closing it.

<!-- gh-comment-id:437692979 --> @brentvollebregt commented on GitHub (Nov 11, 2018): With no information on properly reproducing this and no stack trace or individual error given, then I am going to close this issue as nothing can come out of this. I believe that if you executed this script using something that will preserve output (like the terminal/cmd) you will find that an error is appearing. This script keeps alive from a blocking statement, thus will only stop once the blocking conditions are no longer met (managed by Eel) or an error has occurred; I believe the latter is occurring. If you do decide to preserve the error, you can comment it and I will look at it. But as of now, this issue provides no information so I am closing it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/auto-py-to-exe#25
No description provided.