Enable testing of py37 release #200
Conversation
Activates py37 target in travis instead of the outdated 3.7-dev version. Signed-off-by: Sorin Sbarnea <ssbarnea@redhat.com>
|
Duplicates #172 |
| env: TOXENV=py37 | ||
| # begin: workaround to enable support for py37: | ||
| sudo: required |
There was a problem hiding this comment.
Travis are now recommending removing the sudo tag.
"If you currently specify sudo: false in your .travis.yml, we recommend removing that configuration"
There was a problem hiding this comment.
I think I addressed that in my PR which is hopefully going to be merged soon
There was a problem hiding this comment.
AFAIK, sudo was needed in order to install the newer py37. If that is not needed anymore we can drop it.
Travis recommented not using sudo from day one but reality is that quite often I faced myself in cases where sudo was mandatory for testing some stuff.
There was a problem hiding this comment.
Travis CI sunsetted their container-based infra. Everyone gets VMs now. So this option is basically garbage, therefore.
There was a problem hiding this comment.
Ouch.... not sure what to say about that. While I am fully aware that there are jobs that may not work as docker containers, they count probably for les that 0.1%. I guess it translates to "we failed to manage a production cluster". I guess it goes along the line with https://www.reddit.com/r/programming/comments/8avdrl/travis_ci_dropped_production_database_by/ :)
I guess i need to start using a rss client again as I missed it https://blog.travis-ci.com/2018-10-04-combining-linux-infrastructures
|
Thanks! This was fixed by #345 meanwhile |
Activates py37 target in travis instead of the outdated 3.7-dev version.
Signed-off-by: Sorin Sbarnea ssbarnea@redhat.com