Add support for Django 2.0 #85
Conversation
CHANGELOG.md
Outdated
| ## 2.0.0 | ||
|
|
||
| * Add support for Django 2.0 (#84) | ||
| * Drop support for Django < 1.8 |
CHANGELOG.md
Outdated
| @@ -1,3 +1,8 @@ | |||
| ## 2.0.0 | |||
There was a problem hiding this comment.
I'm not sure if this would be 2.0. Do Django plugins track the main version of Django these days?
There was a problem hiding this comment.
Sorry, just a suggestion. Was inspired by django-extensions, which I noticed went to v2.0 for Django 2.0 -- django-polymorphic is another example. I'll revert changelog changes for now, your guidance welcome.
There was a problem hiding this comment.
The "Drop support for Django < 1.8" is still important though. I'll make sure that gets in. I usually generate changelogs off git history.
danmoz
force-pushed
the
master
branch
5 times, most recently
from
a47a979 to
bc811d6
Compare
| @@ -1,27 +1,37 @@ | |||
| language: python | |||
| # Workaround for Python 3.6 missing | |||
| python: "3.6" | |||
There was a problem hiding this comment.
This was causing all Travis builds to run on Python 3.6, which is probably not what we want... I've updated it to work as intended, its not as pretty but it works
There was a problem hiding this comment.
oh yeah. I've noticed that TravisCI has real support for Python 3.6 now
danmoz
force-pushed
the
master
branch
2 times, most recently
from
539e29b to
f370690
Compare
Adding support for Django 2.0+, and removing support for Django versions up to 1.8, the oldest supported LTS release. This allows us to replace the now deprecated django-extensions UUIDField with the Django native version, and drop a couple of other hacks. Resolves #84