Some Internals Of Django Auth Middleware
In the django.contrib.auth middleware I see the code:
class AuthenticationMiddleware(object): def process_request(self, request): assert hasattr(request, 'session'), "requires session middleware" request.__class__.user = LazyUser() return None
Please avdise me why such a form request._ class _.user = LazyUser() used? Why not just request.user = LazyUser() ?
I know what _ class _ attribute means, but as I undersand direct assignment to instance variable will be better. Where I'm wrong?
LazyUser is descriptor-class. According to documentation it can be only class attribute not instance one:
a.xhas a lookup chain starting with
type(a).__dict__['x'], and continuing through the base classes of
- → What are the pluses/minuses of different ways to configure GPIOs on the Beaglebone Black?
- → Django, code inside <script> tag doesn't work in a template
- → React - Django webpack config with dynamic 'output'
- → GAE Python app - Does URL matter for SEO?
- → Put a Rendered Django Template in Json along with some other items
- → session disappears when request is sent from fetch
- → Python Shopify API output formatted datetime string in django template
- → Shopify app: adding a new shipping address via webhook
- → Shopify + Python library: how to create new shipping address
- → shopify python api: how do add new assets to published theme?
- → Access 'HTTP_X_SHOPIFY_SHOP_API_CALL_LIMIT' with Python Shopify Module