> > One thing to watch out for: ssl.SSLError can't
> > inherit from socket.error, as it does in 2.6+,
>
> Why not?
Mainly because I don't see how to get my hands on the C version of
socket.error. Patches gratefully accepted, though.
Bill
___
Python-De
On 10/18/07, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > > One thing to watch out for: ssl.SSLError can't
> > > inherit from socket.error, as it does in 2.6+,
> >
> > Why not?
>
> Mainly because I don't see how to get my hands on the C version of
> socket.error. Patches gratefully accepted, though
> For anyone who wants to write the patch, you can obviously either
> expose the variable the exception is stored in globally,
Remember that this is an add-on module, so re-compiling the socket
module code to expose the variable globally would be a rather big
change. Or so it seemed to me when I
> > you can
> > import the socket module and just get socket.error directly off of the
> > module itself.
>
> This is feasible.
In fact, so feasible I've done it. :-).
http://pypi.python.org/pypi/ssl/1.9/
Bill
___
Python-Dev mailing list
Python-Dev@py
On 18/10/2007, Bill Janssen <[EMAIL PROTECTED]> wrote:
> > > you can
> > > import the socket module and just get socket.error directly off of the
> > > module itself.
> >
> > This is feasible.
>
> In fact, so feasible I've done it. :-).
>
> http://pypi.python.org/pypi/ssl/1.9/
On a mostly unrelate
I'd love to know what's "different" about Python 2.4 on Windows that
isn't different in 2.3 and 2.5.
Bill
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/op
