django 2.0 needs support (urls)

[tony]

  File "/Users/me/.local/share/virtualenvs/develtech-oQr_FNyw/lib/python3.6/site-packages/polymorphic/admin/__init__.py", line 8, in <module>
    from .parentadmin import PolymorphicParentModelAdmin
  File "/Users/me/.local/share/virtualenvs/develtech-oQr_FNyw/lib/python3.6/site-packages/polymorphic/admin/parentadmin.py", line 14, in <module>
    from django.core.urlresolvers import RegexURLResolver
ModuleNotFoundError: No module named 'django.core.urlresolvers'

Name: django-polymorphic
Version: 1.3
Summary: Seamless Polymorphic Inheritance for Django Models
Home-page: https://github.com/django-polymorphic/django-polymorphic
Author: Christopher Glass
Author-email: tribaal@gmail.com
License: BSD

https://docs.djangoproject.com/en/2.0/releases/2.0/#simplified-url-routing-syntax

[tony]

Two additional warnings need handling:

Using Python version 2.7.1 from /Users/me/work/python/django-polymorphic/.tox/py27-django110/bin/python2.7
Using Django version 1.10.8 from /Users/me/work/python/django-polymorphic/.tox/py27-django110/lib/python2.7/site-packages/django
/Users/me/work/python/django-polymorphic/.tox/py27-django110/lib/python2.7/site-packages/django/db/models/base.py:349: RemovedInDjango20Warning: Managers from concrete parents will soon qualify as default manage
rs if they appear before any other managers in the MRO. As a result, 'base_objects' declared on 'polymorphic.PolymorphicModel' will no longer be the default manager for 'tests.MROBase2' in favor of 'objects' dec
lared on 'tests.MROBase1'. You can redeclare 'base_objects' on 'MROBase2' to keep things the way they are or you can switch to the new behavior right away by setting `Meta.manager_inheritance_from_future` to `Tr
ue`.
  if not opts.managers or cls._requires_legacy_default_manager():
/Users/me/work/python/django-polymorphic/.tox/py27-django110/lib/python2.7/site-packages/django/db/models/base.py:349: RemovedInDjango20Warning: Managers from concrete parents will soon qualify as default manage
rs. As a result, the 'objects' manager won't be created (or recreated) automatically anymore on 'tests.MgrInheritC' and 'mgrB' declared on 'tests.MgrInheritB' will be promoted to default manager. You can declare
 explicitly `objects = models.Manager()` on 'MgrInheritC' to keep things the way they are or you can switch to the new behavior right away by setting `Meta.manager_inheritance_from_future` to `True`.
  if not opts.managers or cls._requires_legacy_default_manager():

[vdboor]

2.0 support is now merged in, and released!