I recall console=True working OK with my project - it opens the pygame window
of the application, plus an additional console window if the application is
started from the GUI. I don't think there's a fundamental problem using
console=True with pygame.
I haven't seen your code, so I don't know where the problem you experience
could come from. Does a simple 'hello-world' style version of the project work
correctly when packaged? Have you been able to locate what line in the code
causes it to exit quietly or hang like this? I've found in the past that
anything affecting sys.stdin or sys.stdout, for example, should be looked at
with suspicion.
Hope this helps,Rob
On Sunday, 8 May 2016, 5:57, scottmeup <[email protected]> wrote:
Hey, thanks for the reply.
I've tried slightly re-working your spec file to fit my project and freezing
with pyinstall but haven't had much luck so far :(
With console=False the executable seems to quietly exit on launch.
If I set console=True it hangs, as it did before.
Console is something I was hoping to have access to, I'm not sure if that's
a problem? I might have to cut back on some functionality if it isn't
possible.
--
View this message in context:
http://pygame-users.25799.x6.nabble.com/Freezing-Pygame-projects-in-Windows-tp2384p2387.html
Sent from the pygame-users mailing list archive at Nabble.com.
