Separate Django auth module from securepass lib

[andreagrandi]

Django authentication module should stay in a separate package securepass-django-auth and depend on securepass. In Python libs these things are usually separated. Someone could need SecurePass lib to build an API and there is no need for Django code to be there. Don't assume that securepass will be used in Django only, there could be a Flask auth module for example.

[alessio]

Hi Andrea,
And thank you much for taking the time to open this issue and improve SecurePass tools!

Although it's absolutely correct to say that specific things should live in their own package as part of coherent namespaces structure, I don't think it's really worth to separate Django auth from the rest of package right now as the whole codebase is still too tiny, therefore it would not be any real benefit for the SecurePass Django users to install two separate packages instead of one.

However this is definitely a good proposal to take into account for future development so that I'm leaving it open and labelling accordingly. Thanks!