You're not helping, Skip. Can you spend a minute looking at urllib2 and seeing how the two variants of my proposal (pass to constructor vs. pass to connect()) would impact on it?
--Guido On 2/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Guido> Didn't work for me, since my ap is a multi-threaded webserver and > Guido> I only want one specific type of request to time out. > > Understood. > > Guido> I'm not going to change ftplib.py and all the others. > > Also understood. This has, as far as I know, been the response of everybody > who has encountered this problem before. Most people are only interested in > a single protocol (or module) and therefore aren't motivated to change/fix > the other protocols which could benefit from timeouts. After all, who > really wants to update gopherlib? So there is sits. > > Guido> I do think it's relevant to decide whether the timeout should be > Guido> passed to the constructor or to the connect() method. I think it > Guido> may be better to pass the timeout to the constructor. > > Another thing to consider is how this change might percolate up to > urllib/urllib2. (I advocate leaving urllib alone, but urllib2 should > probably grow a timeout feature.) > > Skip > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com