On Tue, 2008-12-16 at 14:38 +0000, Loïc Minier wrote:
>
> I don't think urllib2 will be fixed in the near future, but we could
> look at other means to connect to https for apport (setting up the ssl
> socket manually I guess).
Well, if you were going to do that, why not just do that work in urllib2
instead of apport and then have the resulting work useful to many other
applications? Whether you did the HTTPS support in apport directly or
in urllib2 should be six of one, half dozen of the other so why not aim
for the greater good?
On Tue, 2008-12-16 at 14:38 +0000, Loïc Minier wrote:
>
> I don't think urllib2 will be fixed in the near future, but we could
> look at other means to connect to https for apport (setting up the ssl
> socket manually I guess).
Well, if you were going to do that, why not just do that work in urllib2
instead of apport and then have the resulting work useful to many other
applications? Whether you did the HTTPS support in apport directly or
in urllib2 should be six of one, half dozen of the other so why not aim
for the greater good?