Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2002-December/030837.html below:

[Python-Dev] urllib2.build_opener() broken?

• Previous message: [Python-Dev] Another approach for the import mechanism
• Next message: [Python-Dev] build_opener() broken
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'm invoking build_opener() as...

         opener = urllib2.build_opener(proxyHandler)

.... and the handlers appear to be out of order-- the ProxyHandler that 
is supposed to be at the beginning is not ...

[<urllib2.UnknownHandler instance at 0xae6b00>, <urllib2.HTTPHandler 
instance at 0xae6cb0>, <urllib2.HTTPDefaultErrorHandler instance at 
0xae6dd0>, <urllib2.HTTPRedirectHandler instance at 0xae6f60>, 
<urllib2.FTPHandler instance at 0xae6f90>, <urllib2.FileHandler 
instance at 0xae7230>, <urllib2.HTTPSHandler instance at 0xae7320>, 
<urllib2.ProxyHandler instance at 0xae6270>]

 From the comments on build_opener(), it would seem that it doesn't take 
this into account.  However, if it doesn't, then the example used in 
the documentation at the top of urllib2 could not possibly work.

Whose broken?  The module or me?

thanks,
b.bum

• Previous message: [Python-Dev] Another approach for the import mechanism
• Next message: [Python-Dev] build_opener() broken
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4