Test against Django 1.11

[joshblum]

Part of the fix for #80 can be done by using class-based views in Django 1.11

To avoid the possibility of leaking a password reset token via the HTTP Referer header (for example, if the reset page includes a reference to CSS or JavaScript hosted on another domain), the PasswordResetConfirmView (but not the deprecatedpassword_reset_confirm()function-based view) stores the token in a session and redirects to itself to present the password change form to the user without the token in the URL.

https://docs.djangoproject.com/en/1.11/releases/1.11/#django-contrib-auth

[coveralls]

Coverage decreased (-2.2%) to 88.174% when pulling ef43c5c on joshblum:support-django-1.11 into 9a4adc6 on lambdalisue:master.

[coveralls]

Coverage decreased (-2.2%) to 88.174% when pulling e5ba0f3 on joshblum:support-django-1.11 into 9a4adc6 on lambdalisue:master.

[coveralls]

Coverage decreased (-2.2%) to 88.174% when pulling e5ba0f3 on joshblum:support-django-1.11 into 9a4adc6 on lambdalisue:master.

[coveralls]

Coverage decreased (-2.2%) to 88.174% when pulling c44b74b on joshblum:support-django-1.11 into 9a4adc6 on lambdalisue:master.

[coveralls]

Coverage decreased (-2.2%) to 88.174% when pulling c44b74b on joshblum:support-django-1.11 into 9a4adc6 on lambdalisue:master.

[coveralls]

Coverage increased (+0.01%) to 90.424% when pulling de349f0 on joshblum:support-django-1.11 into 9a4adc6 on lambdalisue:master.