[issue837234] Tk.quit and sys.exit cause Fatal Error

Changes by Georg Brandl <[EMAIL PROTECTED]>: -- resolution: -> duplicate status: pending -> closed superseder: -> Tk.quit leads to crash in python.exe ___ Python tracker <[EMAIL PROTECTED]> __

[issue837234] Tk.quit and sys.exit cause Fatal Error

Matthias Kievernagel <[EMAIL PROTECTED]> added the comment: Hi, found a related (duplicate ?) issue which mentions a platform and has code producing the error: http://bugs.python.org/issue775544 Can someone based on WinXP try the code? Attaching it here for easier reference. Works without prob

[issue837234] Tk.quit and sys.exit cause Fatal Error

Pedro Werneck <[EMAIL PROTECTED]> added the comment: I tried reproducing the bug with the info provided but neither case worked. Since it doesn't mention platform, I'm including the file in case anyone wants to try it on anything other than Linux/Python2.5. -- nosy: +werneck Added file:

[issue837234] Tk.quit and sys.exit cause Fatal Error

Sean Reifschneider added the comment: blaforge: I know it's been years, but can you provide code that reproduces this? I'm going to switch it to "pending" state, please re-open when you include some code to reproduce it. -- status: open -> pending T

[issue837234] Tk.quit and sys.exit cause Fatal Error

Martin v. Löwis added the comment: It should not be possible to trigger Py_FatalError through pure Python code. I still haven't tried reproducing the problem, but if it is reproducable, it's a bug. Tracker <[EMAIL PROTECTED]>

[issue837234] Tk.quit and sys.exit cause Fatal Error

Sean Reifschneider added the comment: Is this a bug or just incorrect usage? From reading the message it sounds like it may just have been an incorrect usage. If it's a bug, can we get a sample that reproduces the problem? -- nosy: +jafo Tracker <[