This appears to be an issue with Django in Python 3.6 that doesn't impact 3.5. Downgrading from 3.6.x to 3.5.x should result in this going away, though it's not clear from your post whether it's actually causing problems at runtime or whether it's just an incorrectly triggered warning.