-
Notifications
You must be signed in to change notification settings - Fork 723
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
Comments
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 |
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 |
@BanzaiMan Do we have an ETA for PyPy3 v5.5.0 ? |
BTW PyPy 5.6.0 is out, PR updated accordingly. |
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).
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).
"pypy3" is outdated (Python 3.2), and virtualenv dropped support for it. travis-ci/travis-ci#6727 tracks adding 5.5.
What is the status of this issue? Is there a workaround to get the newer versions in-between? |
I had to remove/deactivate pypy3 builds for pytest-django. |
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 |
@peterjc I just tried your command for PyPy3 but it failed https://travis-ci.org/ofek/privy/jobs/201611336. Did I miss something? |
@ofek Sorry, I'm assuming |
@peterjc That worked, thank you! |
Seems to be required for later versions of pip: travis-ci/travis-ci#6727
Seems to be required for later versions of pip: travis-ci/travis-ci#6727
These runtimes are available for on-demand installation: For Precise
For Trusty
|
Thanks for pointing that out. Can this be added to the official docs too, please? :) |
See travis-ci/travis-ci#6727 for more info too
The list of currently-supported environments can be found at travis-ci/travis-ci#6727 (comment).
* 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
* 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
Could the newest pypy versions be made available? pypy-5.4.1 and pypy3.3-5.5-alpha
The text was updated successfully, but these errors were encountered: