Context Navigation

Changes between Version 8 and Version 9 of ClassBasedViews

-              v8
+              v9
 Pass around the request object via method arguments, store arbitrary state on the request or a special "state" object or dict that is passed around or attached to the request.
+Document that state should be stored on the request, storing it on the view instance is unsafe. Additionally, override __setattr__ or __setattribute__ to make setting state on self raise an error or warning.
+Document that state should be stored on the request, storing it on the view instance is unsafe. Additionally, override `__setattr__` to make setting state on self raise an error or warning.
+Alternatively, override `__getattr__/__setattr__` to access `self.request.state` under the hood while on the surface it looks as if the state is stored on the view instance.
 Example usage and view would be the same as shown below in "__call__ and copy()".
 …
 Arguments against:
  * It's unusual to have a class where you can't store state on self.
+ * It's unusual to have a class where you can't store state on self while in `__init__`.
 ==== !__call!__() and copy() ====