[issue19012] liburl2: bad proxy configuration throws getaddrinfo error

2013-09-17 Thread Sjoerd

Sjoerd added the comment:

That happens when citing things from the top of my head... it is not liburl2 
but urllib2 that I used, excuse me. (And urlopen instead of openurl...)

From
  http://docs.python.org/2/library/urllib2.html
it seems to be a Standard Library module to me, am I mistaken? If so, how do I 
find the urllib2 maintainers?

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19012
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19012] liburl2: bad proxy configuration throws getaddrinfo error

2013-09-14 Thread R. David Murray

R. David Murray added the comment:

The getaddrinfo error message should *not* refer to proxies, because 
getaddrinfo does not do anything involving proxy configuration.  

Presumably the error occurred when liburl2 tried to resolve the proxy.  So, it 
is liburl2 that needs to make sure that error is placed in a comprehensible 
context.  liburl2 is not an stdlib module.  You should report your problem to 
the liburl2 maintainers.

--
nosy: +r.david.murray
resolution:  - invalid
stage:  - committed/rejected
status: open - closed
versions: +3rd party -Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19012
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue19012] liburl2: bad proxy configuration throws getaddrinfo error

2013-09-13 Thread Sjoerd

New submission from Sjoerd:

I'm sorry for providing very little information, but I don't have the system at 
hand anymore. Therefore I will try to reproduce what I know, hoping that you 
recognise the problem. If not, I will get back to the system and try to obtain 
the necessary information.

Calling liburl2.openurl('http://www.google.com') gave me an getaddrinfo error. 
Therefore, I checked my DNS configuration, which seemed okay and I issued a 
socket.getaddrinfo('www.google.com'), which correctly returned an IP address. 
Finally, I found out that I had an old, non-existing (?) proxy configuration in 
the Windows registry (that indeed turned up when calling liburl2.getproxies()). 
Removing the proxy configuration from my Windows registry solved the problem.

Is it preliminary to conclude that the getaddrinfo error may actually mean 
several things (not only a simple getaddrinfo problem)? If so, I suggest that 
the error message be broadened (DNS lookup or proxy problem), because it took 
me several hours to find the proxy problem.

--
components: Library (Lib)
messages: 197629
nosy: SjoerdOptLand
priority: normal
severity: normal
status: open
title: liburl2: bad proxy configuration throws getaddrinfo error
type: behavior
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19012
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com