Am 03.11.20 um 23:34 schrieb Dennis Lee Bieber:
Out of curiosity, does Python on Linux honor the .pyw extension?
On Windows, .pyw indicates a Python program that implements a GUI and
will NOT make use of console (stdin/stdout/stderr).
On Linux, there is no such distinction. O
On 2020-11-03 20:11, David Burnette wrote:
On Wednesday, April 18, 2007 at 12:33:24 AM UTC-7, Chris wrote:
Hi,
I'm puzzled by some strange behavior when my Python/Tkinter
application quits (on linux): the terminal from which I started Python
is messed up.
If start up python, then import the code
On Wednesday, April 18, 2007 at 12:33:24 AM UTC-7, Chris wrote:
> Hi,
> I'm puzzled by some strange behavior when my Python/Tkinter
> application quits (on linux): the terminal from which I started Python
> is messed up.
> If start up python, then import the code below, then start the program
> wit
On May 7, 10:02 pm, "Hamilton, William " <[EMAIL PROTECTED]> wrote:
> > From: Chris
> > > I'll admit to being surprised at seeing a claim that atkinter
> > > application, started within an interactive session, without a
> mainloop,
> > > even runs... I could see it maybe happening from Idle
> From: Chris
> > I'll admit to being surprised at seeing a claim that a
tkinter
> > application, started within an interactive session, without a
mainloop,
> > even runs... I could see it maybe happening from Idle, since Idle is
> > running a tkinter mainloop, so the application bindings m
On May 5, 2:21 pm, Dennis Lee Bieber <[EMAIL PROTECTED]> wrote:
> On 4 May 2007 19:38:39 -0700, Chris <[EMAIL PROTECTED]> declaimed the
> following in comp.lang.python:
>
>
>
> > Thanks, but I was just explaining why I don't want to call mainloop().
> > In my original example, I can type Applicatio
On May 5, 1:24 am, Dennis Lee Bieber <[EMAIL PROTECTED]> wrote:
> On 4 May 2007 08:02:13 -0700, Chris <[EMAIL PROTECTED]> declaimed the
> following in comp.lang.python:
>
> > Ah, sorry, I wasn't being precise. I meant the python commandline
> > python interpreter.
>
> > So from aterminalI type (for
On May 4, 8:52 pm, "Hamilton, William " <[EMAIL PROTECTED]> wrote:
> > -Original Message-
> > From: Chris
> > Subject: Re: Strange terminal behavior after quittingTkinter
> application
> > Clicking 'Quit' or on the window's 'x' causes the application to quit
> > without messing up the termi
> -Original Message-
> From: Chris
> Subject: Re: Strange terminal behavior after quitting Tkinter
application
> Clicking 'Quit' or on the window's 'x' causes the application to quit
> without messing up the terminal. With root.mainloop() co
(I apologize if some similar version of this message has already
appeared; I've tried several time to post it, seemingly without
success.)
> If that is satisfactory, well and good. However, there
> is a possibility that you may lose some settings that you would
> prefer to keep. The termin
Chris wrote:
> ... Quitting by typing 'sys.exit()' in the interpreter
> also works fine. Only quitting via the GUI seems to cause the
> problem.
As previously stated, I know nothing about Tkinter,
but it definitely looks like there is some cleanup being skipped
on a GUI exit that is in fac
> Is there some Tkinter clean up that you have omitted ?
Not that I know about - I was hoping someone would tell me I'd omitted
something.
> Have you ensured that the clean up runs on both normal
> exit and abnormal exit (eg ^C) ?
(^C doesn't make the application exit, it just rai
Chris wrote:
>
> But does anyone know why the Tkinter program is doing this to the
> terminal in the first place? I don't want to have to tell users of my
> program that they must recover their terminal's sanity each time after
> running my program.
>
I don't know about Tkinter, but my g
> What happens if you type 'stty sane' (and of course, a carriage
> return) afterwards?
The terminal returns to normal, thanks!
But does anyone know why the Tkinter program is doing this to the
terminal in the first place? I don't want to have to tell users of my
program that they must recover t
On Apr 18, 2007, at 2:33 AM, Chris wrote:
>
> I'm puzzled by some strange behavior when my Python/Tkinter
> application quits (on linux): the terminal from which I started Python
> is messed up.
>
> If start up python, then import the code below, then start the program
> with Application(), then
(I'm not sure what happened to the formatting in my post: the
"Tkinter.Button" line should be at the same level of indentation as
the "Tkinter.Tk.__init__" line.)
--
http://mail.python.org/mailman/listinfo/python-list
16 matches
Mail list logo
