Hello Boyuan and Scott, > I was made aware of issues encountered by multiple users due to pycurl using > GnuTLS instead of OpenSSL. Reviewing https://bugs.debian.org/515200 , it > looks like the > only reason of not using OpenSSL is the old OpenSSL licensing issue in the > past.
That bug is 15 years old and you did not mention any details about the issues that you're having. Effectively there is no documented reason to switch to openssl on this bug. Scott, I see that you went ahead and switched to openssl anyway: > I don't have any objections to rebuilding pycurl with openssl. We are close to enabling support to http3 for the gnutls libcurl, so this switch kills any possibility of pycurl supporting http3, at least until openssl gets proper http3 support (might not happen for the next stable release). On the curl side, we are considering switching the default backend used by curl (the cli) for the gnutls one, so we can enable http3. Boyuan, can you provide any details on the issues you found? Otherwise I would recommend staying with gnutls for now and so pycurl will soon make use of a http3-enabled libcurl. Cheers, -- Samuel Henrique <samueloph>
