Message 224734 - Python tracker

Message224734

Author	pitrou
Recipients	Ben.Darnell, christian.heimes, dstufft, ezio.melotti, geertj, giampaolo.rodola, gvanrossum, janssen, pitrou, vstinner, yselivanov
Date	2014-08-04.15:24:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<53DFA59C.2080209@free.fr>
In-reply-to	<1407165700.6.0.15932426212.issue21965@psf.upfronthosting.co.za>

Content
Le 04/08/2014 11:21, Geert Jansen a écrit : > > I realize the above is an abstraction violation between the C and Python level. Now that we have an SSLObject Python level API, I could update the code to store a weakref to the SSLObject in the _SSLSocket (just like it does for SSLSocket). That way I can pass the Python level object into the callback. Any thoughts? I think it would make the exposed API nicer, although the implementation would be a bit uglier. Given Python's philosophy, I think the nicer API wins :-)

Content

Le 04/08/2014 11:21, Geert Jansen a écrit :
>
> I realize the above is an abstraction violation between the C and
Python level. Now that we have an SSLObject Python level API, I could
update the code to store a weakref to the SSLObject in the _SSLSocket
(just like it does for SSLSocket). That way I can pass the Python level
object into the callback. Any thoughts?

I think it would make the exposed API nicer, although the implementation 
would be a bit uglier. Given Python's philosophy, I think the nicer API 
wins :-)

History
Date	User	Action	Args
2014-08-04 15:24:15	pitrou	set	recipients: + pitrou, gvanrossum, geertj, janssen, vstinner, giampaolo.rodola, christian.heimes, ezio.melotti, Ben.Darnell, yselivanov, dstufft
2014-08-04 15:24:15	pitrou	link	issue21965 messages
2014-08-04 15:24:15	pitrou	create