Remove dependency on contrib.sites

[collinanderson]

I would use this and help support it if it didn't have the not-null models.ForeignKey('sites.Site').

Similar to https://code.djangoproject.com/ticket/21381

[claudep]

After Django 1.9 is out, the plan is to publish the last release with Django 1.6 support, then we can start leveraging the migrations framework and work on this issue.

[claudep]

1.6.2 has been released today. We can now drop Django 1.6 and start counting on the migration system to go forward.

[ashwoods]

Do you want to completely drop dependency on SITE, or make it optional?

[hedleyroos]

Dropping sites support means you can't use the app in a multisite system. I would just softcode it to check whether django.contrib.sites is installed and adjust the queries accordingly.

[tisdall]

This shouldn't be too hard to do. For example, calls to sites.shortcuts.get_current_site(request) work regardless of 'sites' being installed. The '0001' migration needs to be changed to not be dependent on 'sites', use of settings.SITE_ID needs changing, and the change to the aforementioned ForeignKey.

Are the devs open to a PR related to this?

[claudep]

If you think your proposal will be able to cope with backwards compatibility, then sure!