Code run from IDLE but not via double-clicking on its *.py

[n00m]

When I double-click on "some.py" file console window appears just for a
moment and right after that it's closed. If this script is started from
inside of IDLE (F5 key) then it executes as it should be (e.g.
executing all its print statements).

Any ideas? OS: Windows; Python 2.3.4. Thanks.

[max]

"n00m" <n0**@narod.r u> wrote in
news:11******** *************@g 47g2000cwa.goog legroups.com:

When I double-click on "some.py" file console window appears just
for a moment and right after that it's closed. If this script is
started from inside of IDLE (F5 key) then it executes as it
should be (e.g. executing all its print statements).

Any ideas? OS: Windows; Python 2.3.4. Thanks.

It's a windows thing. The shell windows opens to run the script in is
closing when the script finishes.

Try opening a shell (Start->Run: cmd.exe on NT/2k/XP or Start->Run:
command.com on 95/98) and then either type the full path to the script
or navigate to it and execute it.

max

[mensanator]

n00m wrote:

When I double-click on "some.py" file console window appears just for a
moment and right after that it's closed. If this script is started from
inside of IDLE (F5 key) then it executes as it should be (e.g.
executing all its print statements).

Any ideas? OS: Windows; Python 2.3.4. Thanks.

Your console window closes when the program terminates.
And no, you won't necessarily see any of your print statements
before the window closed. They were buffered and the window
closed before they could be displayed.

Start a console window manually. From the command prompt,
type

some.py

or

python some.py

[n00m]

Thank you, guys, for your replies!

Now it works!

[n00m]

Oops.. not everything so super as I thought.
Incredible but from command line it results as:

D:\>python23\py thon d:\python23\00\ socket6.py
Traceback (most recent call last):
File "d:\python23\00 \socket6.py", line 1, in ?
import socket, thread
File "D:\Python23\00 \socket.py", line 3, in ?
s1 = socket.socket(s ocket.AF_INET, socket.SOCK_STR EAM)
AttributeError: 'module' object has no attribute 'AF_INET'

D:\>

FROM IDLE 1.0.3 THE SAME SCRIPT WORKS PERFECTLY !!!

WHY ON THE EARTH <'module' object has no attribute 'AF_INET'> ???

[Richie Hindle]

[n00m]

WHY ON THE EARTH <'module' object has no attribute 'AF_INET'> ???

Because you have a socket.py in d:\python23\00 which is being picked up
instead of Python's own socket module. You shouldn't give your modules
the same name as Python's own modules.

--
Richie Hindle
ri****@entrian. com

[n00m]

Richie Hindle wrote:

Because you have a socket.py in d:\python23\00 which is being picked up
instead of Python's own socket module. You shouldn't give your modules
the same name as Python's own modules.

Yes, Richie! YOU are dmndly RIGHT! Thanks.

[n00m]

Funnily but I still can't get the code working... WITHOUT IDLE.
I think it's because of "import thread" line. Seems something
wrong with "opening" this module. In IDLE it works OK.

[Richie Hindle]

[n00m]

Funnily but I still can't get the code working... WITHOUT IDLE.
I think it's because of "import thread" line. Seems something
wrong with "opening" this module. In IDLE it works OK.

It's difficult to diagnose your problem with so little information. Please
post:

o The command you're typing into the command prompt
o The error message you're getting
o The full traceback
o The code you're trying to run, or if it's too big then the piece that
the last line of the traceback refers to

Thanks,

--
Richie Hindle
ri****@entrian. com

[Steve Holden]

n00m wrote:

Funnily but I still can't get the code working... WITHOUT IDLE.
I think it's because of "import thread" line. Seems something
wrong with "opening" this module. In IDLE it works OK.

Now, let's see ... [presses fingers to temples and exercises psychic
powers] ... ah yes, its because you're DOING SOMETHING WRONG :-)

Unfortunately "can't get the code working" isn't a very helpful
description. Can you explain (preferably with a traceback) how it fails?

Generally speaking, when you take your car into the garage (American:
shop) because "it won't go" it's OK because the technicians can try and
start it themselves. We don;t have your code readily to hand, so we need
a bit more to go on.

Generally speaking you would do well to try the threading module rather
than thread unless you have a specific reason for not doing so. But if
you post your code (or even better a subset of your code that
demonstrates the error so people can pick it apart for themselves) with
a traceback from the interpreter or a full description of what you
expected the code to do and what it actually does we'll be able to help
much more easily.

regards
Steve
--
Steve Holden [phone] [phone]
Holden Web LLC http://www.holdenweb.com/