Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add pypy 5.6 and pypy3 5.5-alpha #6727

Closed
scop opened this issue Oct 14, 2016 · 12 comments
Closed

Add pypy 5.6 and pypy3 5.5-alpha #6727

scop opened this issue Oct 14, 2016 · 12 comments
Labels

Comments

@scop
Copy link

scop commented Oct 14, 2016

Could the newest pypy versions be made available? pypy-5.4.1 and pypy3.3-5.5-alpha

@yan12125
Copy link

PyPy3 5.5.0 is released, too: https://morepypy.blogspot.tw/2016/10/pypy3-550-released.html

Need the latest PyPy3 as it's the first version with Python 3.3 compatibility, and virtualenv has dropped support for Python3 <= 3.2: https://travis-ci.org/pypa/virtualenv/jobs/174835532

pyenv is not ready yet, so I opened an issue there: pyenv/pyenv#748

@yan12125
Copy link

As stated in https://bitbucket.org/pypy/pypy/issues/2431/is-there-a-pypy33-550-release, the latest revision on py3k branch of pypy is 5.5.0 alpha. The question is: does Travis CI accept alpha softwares? If so, solving this issue is simply upgrading pyenv to v1.0.3, which includes PyPy3 5.5.0 alpha

@ofek
Copy link

ofek commented Nov 13, 2016

@BanzaiMan Do we have an ETA for PyPy3 v5.5.0 ?

@scop scop changed the title Add pypy 5.4.1 and pypy3 5.5-alpha Add pypy 5.6 and pypy3 5.5-alpha Nov 14, 2016
@scop
Copy link
Author

scop commented Nov 14, 2016

BTW PyPy 5.6.0 is out, PR updated accordingly.

nicolaiarocci added a commit to pyeve/cerberus that referenced this issue Nov 19, 2016
Currently Travis has an issue with pypy3 builds, see:

travis-ci/travis-ci#6727

Once this has been fixed on travis we can restart testing against it.
Please note that 'tox -e pypy3' still works locally, so your PRs will
still be checked against pypy3 before a merge (so make sure it passes).
nicolaiarocci added a commit to pyeve/cerberus that referenced this issue Nov 19, 2016
Currently Travis has an issue with pypy3 builds, see:

travis-ci/travis-ci#6727

Once this has been fixed on travis we can restart testing against it.
Please note that 'tox -e pypy3' still works locally, so your PRs will
still be checked against pypy3 before a merge (so make sure it passes).
jedie added a commit to jedie/bootstrap_env that referenced this issue Nov 30, 2016
blueyed added a commit to blueyed/pytest-django that referenced this issue Jan 9, 2017
"pypy3" is outdated (Python 3.2), and virtualenv dropped support for it.

travis-ci/travis-ci#6727 tracks adding 5.5.
@icemac
Copy link

icemac commented Feb 1, 2017

What is the status of this issue? Is there a workaround to get the newer versions in-between?

@blueyed
Copy link

blueyed commented Feb 1, 2017

I had to remove/deactivate pypy3 builds for pytest-django.
Tried to debug/upgrade it a while ago, but gave up for then: pytest-dev/pytest-django#445.

@peterjc
Copy link

peterjc commented Feb 14, 2017

I've just adopted a hack in order to test with PyPy 5.6 and PyPy3.3 v5.5 alpha, early days but it seems to work so far: biopython/biopython@4b4902f

This adds approx 10 to 12s to the builds, eg https://travis-ci.org/biopython/biopython/builds/201561468

@ofek
Copy link

ofek commented Feb 14, 2017

@peterjc I just tried your command for PyPy3 but it failed https://travis-ci.org/ofek/privy/jobs/201611336. Did I miss something?

@peterjc
Copy link

peterjc commented Feb 14, 2017

@ofek Sorry, I'm assuming $HOME/bin is setup and on the path. You could make the symlink under the downloaded bin folder instead - because I add that to the $PATH too.

@ofek
Copy link

ofek commented Feb 14, 2017

@peterjc That worked, thank you!

secretmike added a commit to secretmike/repoze.tm2 that referenced this issue Mar 21, 2017
Seems to be required for later versions of pip:
travis-ci/travis-ci#6727
secretmike added a commit to secretmike/repoze.tm2 that referenced this issue Mar 21, 2017
Seems to be required for later versions of pip:
travis-ci/travis-ci#6727
@BanzaiMan
Copy link
Contributor

These runtimes are available for on-demand installation:

For Precise

$ aws s3 ls s3://travis-python-archives/binaries/ubuntu/12.04/x86_64/ | grep pypy.*bz2$
2015-11-02 11:23:02   24721563 pypy-2.6.1.tar.bz2
2015-12-20 21:39:16   25425728 pypy-4.0.1.tar.bz2
2015-12-20 21:39:16   25425728 pypy-4.0.tar.bz2
2016-07-08 01:14:27   28990441 pypy-5.0.0.tar.bz2
2016-07-08 01:23:58   28920422 pypy-5.0.1.tar.bz2
2016-07-08 01:21:35   29039673 pypy-5.1.1.tar.bz2
2016-07-08 01:21:49   29094467 pypy-5.1.tar.bz2
2016-07-08 01:18:24   33100456 pypy-5.3.1.tar.bz2
2016-07-08 01:22:47   33113882 pypy-5.3.tar.bz2
2016-11-09 17:29:25   33614598 pypy-5.4.1.tar.bz2
2016-09-08 04:55:35   33571606 pypy-5.4.tar.bz2
2017-06-05 23:57:16   29295218 pypy-5.6.0.tar.bz2
2017-06-05 23:57:16   29295218 pypy-5.6.tar.bz2
2016-09-07 22:10:25   35466496 pypy3-2.4.0.tar.bz2
2015-12-20 21:42:38   35064187 pypy3-2.4.tar.bz2
2016-07-12 15:47:52   31092855 pypy3.3-5.2-alpha1.tar.bz2
2017-03-08 23:09:08   26550720 pypy3.3-5.5-alpha.tar.bz2

For Trusty

$ aws s3 ls s3://travis-python-archives/binaries/ubuntu/14.04/x86_64/ | grep pypy.*bz2$
2015-11-02 11:23:12   27706390 pypy-2.6.1.tar.bz2
2015-12-20 21:39:09   25482627 pypy-4.0.1.tar.bz2
2015-12-20 21:39:09   25482627 pypy-4.0.tar.bz2
2016-07-08 01:12:53   28912705 pypy-5.0.0.tar.bz2
2016-07-08 01:24:09   28923467 pypy-5.0.1.tar.bz2
2016-07-08 01:21:36   29015127 pypy-5.1.1.tar.bz2
2016-07-08 01:25:50   29111536 pypy-5.1.tar.bz2
2016-07-08 01:27:40   33130244 pypy-5.3.1.tar.bz2
2016-07-08 01:23:30   33149149 pypy-5.3.tar.bz2
2016-11-09 17:30:26   33625737 pypy-5.4.1.tar.bz2
2016-09-08 04:55:55   33515769 pypy-5.4.tar.bz2
2017-06-05 23:57:09   29302524 pypy-5.6.0.tar.bz2
2017-06-05 23:57:08   29302524 pypy-5.6.tar.bz2
2017-06-05 23:57:46   29048662 pypy-5.7.1.tar.bz2
2017-06-05 23:57:46   29048662 pypy-5.7.tar.bz2
2016-09-07 22:10:32   42801682 pypy3-2.4.0.tar.bz2
2015-12-20 21:42:15   41986352 pypy3-2.4.tar.bz2
2016-07-12 15:48:47   31161218 pypy3.3-5.2-alpha1.tar.bz2
2017-03-08 23:09:11   26665269 pypy3.3-5.5-alpha.tar.bz2

@WhyNotHugo
Copy link

Thanks for pointing that out. Can this be added to the official docs too, please? :)

jsmnbom added a commit to python-telegram-bot/python-telegram-bot that referenced this issue Jun 22, 2017
flother pushed a commit to JaGallup/spaceland that referenced this issue Jul 10, 2017
The list of currently-supported environments can be found at
travis-ci/travis-ci#6727 (comment).
texasaggie97-zz pushed a commit to ni/nimi-python that referenced this issue Jul 12, 2017
marcoskirsch pushed a commit to ni/nimi-python that referenced this issue Jul 13, 2017
* Use trusty distribution (underlying OS image) since it has Python 3.5 & 3.6 in the image

* Python 2.7 doesn't take an encoding

* Use TravisCI to iterate over all versions of Python

* Use python instead of python3 to get the default python

* Use correct names/versions for pypy

per travis-ci/travis-ci#6727

* Use 5.6.0

* Add formatted information about parameter that causes assert

* Use == instead of is for string

* Use == and != instead of is and is not

* pypy3 just doesn't seem to work

* Try a different pypy3

* Missed merge conflict
marcoskirsch pushed a commit to ni/nimi-python that referenced this issue Jul 17, 2017
* Use trusty distribution (underlying OS image) since it has Python 3.5 & 3.6 in the image

* Python 2.7 doesn't take an encoding

* Use TravisCI to iterate over all versions of Python

* Use python instead of python3 to get the default python

* Use correct names/versions for pypy

per travis-ci/travis-ci#6727

* Use 5.6.0

* Add formatted information about parameter that causes assert

* Use == instead of is for string

* Use == and != instead of is and is not

* pypy3 just doesn't seem to work

* Try a different pypy3

* Missed merge conflict

* Don't ignore command_history.txt any more

* Add update_generated_files as a possible target

* Copies code generated files into generated/<driver>
* Delete command_history.txt before running any commands
* Required since log_command just appends

* Generated files

* Create batch and shell script both for command histiry

* Sort items so that changes in order won't cause random changes in generated files
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants