Skip to content

Remove python 3.4 from travis. #275

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

Merged
merged 1 commit into from
Jul 12, 2021

Conversation

xkdcc
Copy link
Contributor

@xkdcc xkdcc commented May 8, 2021

This is to fix Travis CI failure which has been seen in all PRs since 2020!
The error message in CI job as below:

Collecting PyYAML (from python-coveralls)
  Downloading https://files.pythonhosted.org/packages/64/c2/b80047c7ac2478f9501676c988a5411ed5572f35d1beff9cae07d321512c/PyYAML-5.3.1.tar.gz (269kB)
PyYAML requires Python '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*, !=3.4.*' but the running Python is 3.4.8

The root cause of Travis CI failures is that, it will install python-coveralls latest version 2.9.3.
However, on PyPI python-coveralls 2.9.3, it has dropped Python 3.4 support.

@zongkaixuan
Copy link

Hi Brant,

I submitted a PR but seems like still failed for python 3.4 from travis. :P
https://travis-ci.org/github/aliyun/aliyun-oss-python-sdk/builds/771917170?utm_source=github_status&utm_medium=notification

"PyYAML requires Python '>=2.7, !=3.0., !=3.1., !=3.2., !=3.3., !=3.4.*' but the running Python is 3.4.8"

Thanks,

@huiguangjun huiguangjun merged commit c34c10c into aliyun:master Jul 12, 2021
@xkdcc
Copy link
Contributor Author

xkdcc commented Jul 13, 2021

Hi Brant,

I submitted a PR but seems like still failed for python 3.4 from travis. :P
https://travis-ci.org/github/aliyun/aliyun-oss-python-sdk/builds/771917170?utm_source=github_status&utm_medium=notification

"PyYAML requires Python '>=2.7, !=3.0., !=3.1., !=3.2., !=3.3., !=3.4.*' but the running Python is 3.4.8"

Thanks,

Hi @zongkaixuan ,

When you submitted your PR, my PR (changes to remove Python 3.4) had not yet merged!
That's why you're seeing failures.
Now it should work as @huiguangjun has just merged it yesterday.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants