[Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy? (original) (raw)
Joni Orponen j.orponen at 4teamwork.ch
Mon Jan 22 07:48:26 EST 2018
- Previous message (by thread): [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?
- Next message (by thread): [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Jan 22, 2018 at 11:59 AM, Oleg Broytman <phd at phdru.name> wrote:
On Mon, Jan 22, 2018 at 02:33:01AM -0800, Larry Hastings <_ _larry at hastings.org> wrote: > All ... CI tests fail in > the same way, reporting this error: > > The command "pyenv global system 3.5" failed and exited with 1 during .
Seems there is a slow workaround (install python 3.5): https://github.com/travis-ci/travis-ci/issues/8363#issuecomment-354857845 which python3.5 || (pyenv install 3.5.4 && pyenv use system 3.5.4)
There is also https://github.com/praekeltfoundation/travis-pyenv I've found useful when one needs excactness and also to decouple oneself from the Travis side rolling releases of Python. Also caches the Python version for you.
See https://github.com/plone/plone.intelligenttext/blob/a71bdc5b485b1562b2e320f5c41a15286f205f98/.travis.yml for a usage example.
-- Joni Orponen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180122/14e31789/attachment.html>
- Previous message (by thread): [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?
- Next message (by thread): [Python-Dev] Slipping Python 3.5.5rc1 and 3.4.8rc1 because of a Travis CI issue--can someone make Travis CI happy?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]