Skip to content
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

Support Django 2.0 #75

Merged
merged 9 commits into from
Feb 26, 2018
Merged

Support Django 2.0 #75

merged 9 commits into from
Feb 26, 2018

Conversation

jwhitlock
Copy link
Member

Django 2.0a1, the first alpha release, is now available.

  • Use the standard Manager/Queryset in Django 2.0. Continue using GeoManager and GeoQueryset in previous versions. Note: We may be able to use the standard versions as far back as 1.8., if we're willing to take a version bump.
  • Use the new field API for relationship fields

@coveralls
Copy link

coveralls commented Sep 25, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling c5db864 on jwhitlock:django-2.0 into f104c09 on tulsawebdevs:master.

@coveralls
Copy link

coveralls commented Sep 25, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 0248205 on jwhitlock:django-2.0 into f104c09 on tulsawebdevs:master.

@coveralls
Copy link

coveralls commented Sep 25, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling 21d55d7 on jwhitlock:django-2.0 into f104c09 on tulsawebdevs:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 86e8460 on jwhitlock:django-2.0 into f104c09 on tulsawebdevs:master.

@jwhitlock jwhitlock merged commit 7d30696 into tulsawebdevs:master Feb 26, 2018
@jwhitlock jwhitlock deleted the django-2.0 branch February 26, 2018 00:41
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.

None yet

2 participants