Support PyPy 2.0

[dstufft]

It would be great if Travis supported PyPy 2.0 (http://doc.pypy.org/en/latest/release-2.0.0.html).

[roidrage]

We'd love to! Is there a known APT repository we could use for installation?

[stefanor]

It'll be in https://launchpad.net/~pypy/+archive/ppa eventually. But the PPA build queue is really long at the moment, and it usually takes several retries to find a builder with enough RAM...

[stefanor]

It's published: https://launchpad.net/~pypy/+archive/ppa

[jstasiak]

+1

[glyph]

+1

[glyph]

In addition to the aforementioned issue with treq being unable to verify support for a recent version of PyPy, there's also the issue that PyPy 1.9 segfaults even when running "vanilla" Python code, such as pep8.py. In this build you can see that happening: https://travis-ci.org/dreid/treq/jobs/8835621#L203

When we asked a PyPy maintainer about it, the reply was "1.9 is ancient, we know it segfaults. make them upgrade to 2.0.2".

[joshk]

I will look into this hopefully later this week.

Sorry for the delay.

On 8/07/2013, at 6:48 PM, Glyph notifications@github.com wrote:

In addition to the aforementioned issue with treq being unable to verify support for a recent version of PyPy, there's also the issue that PyPy 1.9 segfaults even when running "vanilla" Python code, such as pep8.py. In this build you can see that happening: https://travis-ci.org/dreid/treq/jobs/8835621#L203

When we asked a PyPy maintainer about it, the reply was "1.9 is ancient, we know it segfaults. make them upgrade to 2.0.2".

—
Reply to this email directly or view it on GitHub.

[glyph]

Thanks for looking into it.

[jodal]

Any progress on this?

[joshk]

Sorry, things have been a bit crazy and I haven't had time to dig deeper into this yet.

On 31/07/2013, at 12:56 AM, Stein Magnus Jodal notifications@github.com wrote:

Any progress on this?

—
Reply to this email directly or view it on GitHub.

[nandoflorestan]

+1 for having a recent version of PyPy on travis

[squeaky-pl]

Note that PyPy 2.1 final is already out. http://morepypy.blogspot.com.es/2013/08/pypy-21-considered-armful.html

[dstufft]

@joshk Wondering if you've had a chance to dig deeper into this yet?

[thedrow]

+1

[andrewsmedina]

+1

[benoitc]

+1

[jodal]

As of yesterday, PyPy 2.1 Debian packages are available from the PyPy PPA.

Both PyPy 2.0 and 2.1 target compatibility with CPython 2.7.3, just like PyPy 1.9, which is currently used by Travis, does. In other words, it should be straight forward to upgrade the Travis build environments from PyPy 1.9 to 2.1.

PyPy 1.9 was released back in June 2012, and has long been considered old by the core developers of the fast moving PyPy project. It is today largely unsupported.

Please upgrade Travis' build environment to provide PyPy 2.1 instead of 1.9.

[dstufft]

So I've worked up a workaround to this with a gotcha.

You can see the workaround here https://github.com/alex/cryptography/pull/62, which works by installing the latest PyPy from PPA and removing the preinstalled one. However if you're using built in travis support for PyPy you'll probably need to delete the pypy virtualenv and recreate it. If you're using tox it creates a new virtualenv as part of running the tests so the Travis supplied virtualenv doesn't get used.

[joshk]

This will be supported in the next VM release :)

Blog post next week about the changes.

[thedrow]

Awesome!

[sn6uv]

@joshk Any progress on this? I see there was a blog post on October 14th, but no mention of PyPy.

[thedrow]

@joshk Is it out yet?

[joshk]

Not yet, it got delayed, the new VMs are finalised so I am in the process of writing a blog post about the upgrades. :)

On 5/11/2013, at 6:09 pm, Omer Katz notifications@github.com wrote:

@joshk Is it out yet?

—
Reply to this email directly or view it on GitHub.

[nandoflorestan]

Not yet, it got delayed, the new VMs are finalised

Thanks!!!

[thedrow]

@joshk Right now my build fails with PyPy 1.9 but I don't care about it. I want to support PyPy 2.0 and above.

[alex]

FYI: PyPy 2.2 has been released, and is now available from the same PPA.

[peterjc]

TravisCI now supports PyPy 2.2, so this issue can be probably closed:
http://about.travis-ci.org/blog/2013-11-18-upcoming-build-environment-updates/

[joshk]

Closed :)

[jstasiak]

Cheers!