> Code run from IDLE but not via double-clicking on its *.py
It still does not work. Weird.
--
http://mail.python.org/mailman/listinfo/python-list
Dennis Lee Bieber wrote:
> Hope you'll forgive my comment -- but for some reason those look...
Your comments are absolutely relevant.
> My version, using select(), shouldn't have this problem.
Now I see what you meant ("You need no threads"). Your code works just
fine (hope over LAN too). I correc
I wrote:
> I prefer the tread solution. You can see my exmaple
> in message <[EMAIL PROTECTED]>.
>
>http://groups.google.com/group/comp.lang.python/msg/ffd0159eb52c1b49
[...]
> you should send the shutdown
> across, much like you copy data across: shutdown writing on the
> other socket.
Whic
Dennis Lee Bieber wrote:
> I'm going to go back a few messages... Looking for a
> simplification...
[...]
> TWO threads, both just infinite loops of the same nature (you could
> actually have done ONE def and passed different arguments in to
> differentiate the two thread invocations
Dennis:
> However, threads aren't really needed for this simple connection
> relay... The following has /not/ been run (since I don't have your
> server nor VBS) but should do about the same thing (see comments for one
> lack).
To some degree you are right!
If the vbs issues only some "primitive"
LOL... seems it disappears only in Win98. In Win2k it goes like this:
C:\>d:
D:\>python23\python d:\python23\socket6.py
D:\>
> C:\> d:
> D:\> cd \python23
> D:\> python d:\python23\socket6.py > out.txt 2> err.txt
> Does anything appear in d:\python23\out.txt or d:\python23\err.txt?
NOTHING APPEA
[Richie]
> Now what does the python Command Prompt say?
[n00m]
> It says... NOTHING! It just DISAPPEARS!
That's the strangest thing I've heard all week. 8-)
OK, one more thing to try - redirect the output of Python to some files
and see whether anything useful appears in the files:
C:\> d:
D:
Dennis; Richie;
>That sounds impossible, so I must be misunderstanding something.
YOU - BOTH - UNDERSTAND ME ABSOLUTELY RIGHT!
>1.
>Start a new Command Prompt via Start / Programs / Accessories / Command
>Prompt (or the equivalent on your machine)
>2.
>Type the following: d:\python23\python d:\pyt
It's soo pity I'm too buzy at my work today.
I'll reply a bit later. Thank you, guys!
PS Port 1433 SQL Server listens to.
PPS SQL Server is a rdbms from M$.
--
http://mail.python.org/mailman/listinfo/python-list
[n00m]
> D:\>python23\python d:\python23\socket6.py [Enter]
>
> It's OK so far. Python code is launched and starts listening
> to port 1434 (see the code below; it's the same code as in my
> neibouring topic).
> Now I launch a vbs script (which will connect to port 1434).
> I.e. I just double-cli
Steve Holden wrote:
> Now, let's see ... [presses fingers to temples and exercises psychic
> powers] ... ah yes, its because you're DOING SOMETHING WRONG :-)
I just admire this sort of humour!
Made me chuckling and (even) laughing.
--
http://mail.python.org/mailman/listinfo/python-list
Richie; Steve; Thanks for your replies!
> 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
1.
D:\>python23\pyt
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 be
[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
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.
--
http://mail.python.org/mailman/listinfo/python-list
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.
--
http://mail.python.org/mailman/listinfo
[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
[EMAIL PROTECTED]
--
Oops.. not everything so super as I thought.
Incredible but from command line it results as:
D:\>python23\python 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 ?
Thank you, guys, for your replies!
Now it works!
--
http://mail.python.org/mailman/listinfo/python-list
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
"n00m" <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> 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 prin
21 matches
Mail list logo
