I have to say, having settings as Python code is one of the features of
Django for me. Being able to calculate settings values, take advantage of
Python’s module/class parsing, and so on all make settings more than just a
set of dictionary values. I think we would lose a bit of functionality i
Many of these auth systems are client/server, not going to be the simplest
thing to configure the entire stack for simple projects/tutorials/testing
environments and so on. I can definitely see having.a pluggable alternative to
the contrib.auth package that implements all the client-side stuff,
I agree, -1, for composability. I must also say, I find the current idiom
easier to read than the proposed version, but by far the more important factor
to me is the violation of composability by bundling different kinds of
functionality into one call. One of the nice features of querysets.
-
