I'm not affiliated to @maxtepkeev, but I ran the travis tests for Django on all supported versions and ALL except for Python 3.4 with MySQL (PostgreSQL works fine) work fine. I recommend you just get Travis from GitHub's market, create your own repository, and debug from there by testing everything on your repository and copying the files to your Django app. For EVERYONE though, your .travis.yml should NOW include:
I changed PyMySQL to mysqlclient since Django kept raising that error (I only tested on Django). Additionally, with my other repository, Django-cachalot, there seems to be this consistent error with Python 3.4 and MySQL so you should avoid it in general. You should be able to figure out how travis's files work. For other Djangonauts, this is my travis config file:
I'm not affiliated to @maxtepkeev, but I ran the travis tests for Django on all supported versions and ALL except for Python 3.4 with MySQL (PostgreSQL works fine) work fine. I recommend you just get Travis from GitHub's market, create your own repository, and debug from there by testing everything on your repository and copying the files to your Django app. For EVERYONE though, your
.travis.yml
should NOW include:I changed PyMySQL to mysqlclient since Django kept raising that error (I only tested on Django). Additionally, with my other repository, Django-cachalot, there seems to be this consistent error with Python 3.4 and MySQL so you should avoid it in general. You should be able to figure out how travis's files work. For other Djangonauts, this is my travis config file:
Again they all worked fine except for python 3.4 with MySQL:
![IMG_2331](https://user-images.githubusercontent.com/60190294/77370213-cd679280-6d36-11ea-811b-c4951933743e.JPG)