Python 3.5 failing on download in bionic

Languages Python
1

Hi,

Our build on python 3.5 started failing just now. You can find the job here. The yaml is as follows:

- language: python
  python: 3.5
  os: linux
  dist: bionic

The log is:

3.5 is not installed; attempting download
Downloading archive: https://storage.googleapis.com/travis-ci-language-archives/python/binaries/ubuntu/18.04/x86_64/python-3.5.tar.bz2
0.06s$ curl -sSf -o python-3.5.tar.bz2 ${archive_url}
curl: (22) The requested URL returned error: 404
Unable to download 3.5 archive. The archive may not exist. Please consider a different version.

I checked and the file does indeed not exist. Is this an issue on my part?

2

Try newer Pythons (3.6+) on Bionic.

3

I don’t understand. Does this mean that 3.5 is not supported there? Is this documented somewhere? I didn’t see any deprecation notice and 3.5 worked just a few days ago.

So I checked and replacing 3.5 with 3.6 the url works, but then replacing it with 3.7 doesn’t work again. I’m not sure what to make of this.

4

Somehow 3.7 archive was missing. (3.7.3 should work, though) I initiated https://travis-ci.org/travis-ci/cpython-builder/builds/548373093. This should make the 3.7 archive available in about 24 hours.

1 Like
5

Sorry, the original question was about Python 3.5 and not 3.7; we’re also influenced by this now, can you please provide an update?

Is 3.5 not meant to be used with bionic?

6

A search in the Ubuntu package library shows that Xenial is the last release supporting Python 3.5. (search result)

If you need to continue supporting v3.5, run those tests on Xenial.
You can’t reasonably expect users with newer systems to run such old Python releases anyway.

7

I understand that. However as @matham wrote above, python 3.5 was working with bionic until a few days ago. I therefore wanted to know if indeed the support is meant to be discontinued or is that an oversight.

8

There was an issue where jobs with dist: bionic would actually be run in previous releases. If you look at the build logs, you’ll see that. That issue is resolved now AFAICS.

9

Got it, thanks!