> I'm very tempted to add an optional parameter to socket.ssl(), which
> will be a callback function which will be passed the remote side's IP
> address and credentials, and which may raise an exception if it
> doesn't like the credentials. The exception would then be re-raised
> from socket.ssl()
O.R.Senthil Kumaran schrieb:
> Hello All,
>
> I am drafting a PEP proposing a module 'urilib', which will be the unified
> module of urlparse, urllib and urllib2.
>
> a) _all_ functions will include from urlparse,urllib and urllib2. b)
> overlapping functionality between urllib and urllib2 to be
> The idea is that if you call socket.ssl() on a socket that's bound to
> an address, the socket is assumed to be server-side, the cert passed
> in is assumed to be a server-side cert, and the SSLObject returned has
> a couple of extra methods, listen() and accept(). Calling accept() does
> the SS
Hello All,
I am drafting a PEP proposing a module 'urilib', which will be the unified
module of urlparse, urllib and urllib2.
a) _all_ functions will include from urlparse,urllib and urllib2.
b) overlapping functionality between urllib and urllib2 to be ironed out.
c) RFC3986 and RFC3987 complia
