Confusing PyPy versions

[andreif]

In order to run tests with PyPy 3.5, I can just specify it as pypy3.5 as mentioned in the docs at Building a Python Project - Travis CI
In this case the version is:

$ python --version
Python 3.5.3 (3f6eaa010fce, Jan 11 2018, 04:44:35)
[PyPy 5.10.1 with GCC 6.2.0 20160901]

The docs also say that one can test with PyPy (meaning 2.7-x branch I suppose):

Travis CI supports PyPy and PyPy3.

But when one tries to set pypy or pypy2.7, it fails to download it from S3.

I have found that I can get it to work with pyp2.7-6.0 (see https://github.com/travis-ci/travis-ci/issues/9542), but not sure if it’s possible to get 2.7-5.x somehow.

Versions that fail:

  - pypy
  - pypy2
  - pypy2.7
  - pypy2.7-5.10
  - pypy2.7-5.10.1
  - pypy2.7-7.0
  - pypy3
  - pypy3.5-5.10
  - pypy3.5-5.10.1
  - pypy3.5-7.0

Versions that work:

  - pypy2.7-6.0
  - pypy3.5  # == 5.10.1 atm
  - pypy3.5-6.0

The working versions need to be mentioned in the docs at least. Ideally one would want to have an explicit way to select a version, as in case of 6.0. I feel that pypy3.5 archive can get updated to a newer version, but it would be great to be still able to test against 5.x.

Any plans for pypy2.7-7.0 and pypy3.5-7.0?

Similar threads

Add PyPy 7 support

Please add support for the new PyPy 7.0.0 release, at least PyPy3.5 and PyPy2.7: PyPy v7.0.0: triple release of 2.7, 3.5 and 3.6-alpha The PyPy team is proud to release the version 7.0.0 of PyPy, which includes three different interpreters: PyPy2.7, which is an interpreter supporting the syntax and the features of Python 2.7 PyPy3.5, which supports Python 3.5 PyPy3.6-alpha: this is the first official release of PyPy to support 3.6 features, although it is still considered alpha quality. …

Document supported pypy versions

https://docs.travis-ci.com/user/languages/python/#specifying-python-versions has a (supposedly) comprensive list of valid values for the python: field for normal Python. There’s, however, no such list in https://docs.travis-ci.com/user/languages/python/#pypy-support : it only mentions pypy3.5. Distro-specific articles don’t have any comprehensive lists, either. Experiments show that there are no validation checks in the build logic, it just blindly tries to fetch a tarball with the correspondi…

Please allow PyPy to work on Xenial

My builds fail since I added dist: xenial, since PyPy appears unsupported there. Excerpt from a job log: pypy is not installed; attempting download Downloading archive: https://s3.amazonaws.com/travis-python-archives/binaries/ubuntu/16.04/x86_64/pypy.tar.bz2 $ curl -sSf -o pypy.tar.bz2 ${archive_url} curl: (22) The requested URL returned error: 403 Forbidden Unable to download pypy archive. The archive may not exist. Please consider a different version.

PyPy 3.5 v6.0.0: inconsistent OpenSSL bindings

So there’s two xenial jobs with PyPy v6.0.0 set up. But tests are behaving inconsistently. Turns out, that PyPy 2.7 v6.0.0 is linked against OpenSSL 1.1, while pypy2.7-6.0 is not installed; attempting download Downloading archive: https://s3.amazonaws.com/travis-python-archives/binaries/ubuntu/16.04/x86_64/pypy2.7-6.0.tar.bz2 $ curl -sSf -o pypy2.7-6.0.tar.bz2 ${archive_url} $ sudo tar xjf pypy2.7-6.0.tar.bz2 --directory / $ python --version Python 2.7.13 (ab0b9caf307db6592905a80b8faffd69b390…

PyPy 2.7 on Xenial

I’ve noticed that none of these work in dist: xenial builds: python: - pypy - pypy2 - pypy2.7 but the following does work: python: - pypy2.7-5.10.0 That doesn’t seem right? https://github.com/travis-ci/travis-ci/issues/9452 mentioned a similar problem on trusty, and it was a matter of making a copy of the archive somewhere (in the S3 bucket?). (For completeness I should mention that pypy3.5 works, but pypy3 doesn’t. I assume pypy3.5-5.10.0 would also work, but I haven’t needed to …

[webknjaz]

@andreif FTR it should be pypy3.6-7.0.0 (not 3.5) once available.

[andreif]

Lol, thanks!