[Python-bugs-list] [ python-Bugs-785584 ] urllib output: Worker thread..

[SourceForge.net]

Bugs item #785584, was opened at 2003-08-08 19:59
Message generated for change (Comment added) made by netytan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=785584&group_id=5470

Category: Windows
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: mark lee smith (netytan)
Assigned to: Nobody/Anonymous (nobody)
Summary: urllib output: Worker thread..

Initial Comment:
Hi all,

I've used urlib many times before and have never got 
anything like this.. therefore i'm assuming this is a new 
thing in 2.3. because i've only been seeing this since I 
upgraded my Python version. Anyway At the end of a 
program that uses urllib.urlopen() this line appears

Worker thread [ 4291533751 ] : recieved quit event

And even if the program doesn't output anything it still 
appears, it's not really a big problem but it is very 
anoying! If somone could explain it I would much 
appreciate it.

I've attach a sample program (i've tested it with a few 
smaller programs and get the same output)

Mark.

----------------------------------------------------------------------

>Comment By: mark lee smith (netytan)
Date: 2003-08-12 23:53

Message:
Logged In: YES 
user_id=797196

Ok I've spent allot of my free time working on this now and 
I'm pretty sure it isn't in the urllib module. The same message 
is displayed when using smtplib and sendmail. Both modules 
use the socket module, but I am not sure about searching 
that for the message since it is writen in C (A lang' i've only 
brushed with a  few times) plus i'm not sure if this has been 
changed since 2.2.. I could probably upgrade my version at 
home and see if i get the same message but i'm a little 
reluctant to do that.

Sorry cannon, I don't know much about Macs or Mac OS :)

Hope this helps, let me know what you think. Am not sure 
where to go next.

Mark.

----------------------------------------------------------------------

Comment By: Brett Cannon (bcannon)
Date: 2003-08-09 20:25

Message:
Logged In: YES 
user_id=357491

If you could attempt to figure out where the message is coming 
from that would be great since I have no clue what would be 
causing it.

As for the file path thing, I was executing from my CVS directory 
with your files on my desktop so I did not have my working 
directory the same as where the script was.

----------------------------------------------------------------------

Comment By: mark lee smith (netytan)
Date: 2003-08-09 06:50

Message:
Logged In: YES 
user_id=797196

I agree with you.. I have a few box's, the error is on Windows 
me box. I havn't had the oppertunity to upgrade the version 
of Python on my XP box because it is running some fairly 
important stuff i'm working on but I plan on upgrading as soon 
as I can. I have a FreeBSD box aswell but no Python as of 
yet. My friend is running FreeBSD and doesn't see the Worker 
Thread either..

I did the same search after I posted this message yesterday 
and couldnt fine anything either. If take into account my lack 
of copying skills then that could explain the miss spelling, I 
know we do spell some words differently from american 
english.

Thanks for the tip, as far as I'm aware if you open a file with 
just the files names then Python automatically looks in the 
same dir as the script. So i'm a little unsure why I would want 
to use an absolute file name when the file is right there :).

Thanks for your help.
Mark.

 

----------------------------------------------------------------------

Comment By: Brett Cannon (bcannon)
Date: 2003-08-08 21:21

Message:
Logged In: YES 
user_id=357491

On my OS X machine I don't get that message.  What OS are you 
using, Mark?  If you look at urllib it does not import any threading 
module.  I ran ``egrep -r "Worker thread" *`` and it found 
nothing.  Search also failed for "recieved quit event" (which 
"recieved" is misspelled so you would think a search would turn it 
up easily).  I have a sneaking suspicion this might be platform-
specific.

Also, just a tip on opening files relative to the running code: it's 
best to make it absolute by making the path like so:

path = os.path.join(os.path.split(__file__)[0], "file.txt"))

This makes the path absolute so if people (like me) try to execute 
your script from another directory Python doesn't say it can't find 
the file you are referencing.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=785584&group_id=5470