bpo-36307: Upgrade Travis CI to Xenial and rm obsolete sudo:false by CAM-Gerlach · Pull Request #12356 · python/cpython (original) (raw)

Thanks @tirkarthi .

There were Openssl compatibility issues in the past

To note, at least according to the issue you linked, these issues were reported with Trusty, whereas the OpenSSL version distributed with Xenial is compatible. Therefore, we could switch back to the distro-provided version, though it makes sense to keep it building its own version to demonstrate how to do so, exercise that functionality and ensure compatibility with the latest OpenSSL.

While were at it, should we also bump the version up to the latest 1.1.1b, which is the current LTS branch (with 1.0.2 EoL in Dec. 2019 and 1.1.0 EoL in a few months, in September)?

xenial used to be less stable

We will indeed want to confirm this with the relevant parties, as this is not a trivial change, but I do note just based on the thread, the one individual who commented about Xenial not working reliably later took it back, saying it only required extra configuration (which is no longer the case). However, there may be other issues of which I'm aware (we ourselves haven't had any since spyder-ide/spyder#8802 , but obviously we're not exactly CPython).