Hi, Not to offend anyone, but django.contrib.auth is quite limited. At some point I have decided that something should be done with that. Here is my attempt to change something - Talos application. I tried to implement as much as I considered reasonable, but not everything I ever saw in real world. Talos is not and was not planned as drop-in django.contrib.auth replacement. Instead, it is meant to be complex solution for difficult problems, not everyone has. django.contrib.auth does it job well for simple scenarios, which unfortunately are not the ones I have.
This is still work in progress, don't expect anything in particular to work well. But the idea should be clear. I develop using PostgreSQL (authenticated by certificates), Python 3.5/3.6, Django 1.11. Probably one has to change settings.py to something more appropriate to local development environment before running test project. I will not copy-paste README, it is available directly at link, as well as source code with test project. https://github.com/triflesoft/django-application-talos I will be really happy to hear any feedback, advice, questions, comments, etc. Not only about code details, but in general. Maybe something can be done in more djangonic, more pythonic way. Maybe there is some widely used scenario I missed. I want this application to be as good as it can be. Roman P. S. I am no native speaker. If something is written in bad/ambiguous English, I will be glad to correct that too. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/05a3fad6-5e8f-4374-9bcc-74342cc9da24%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
