id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 24121,Provide a better repr() experience,Keryn Knight,Nicolás Restrepo,"For a long time, Django has shipped with the debug 500 handler, which defaults to a view where ""local vars"" for every stack frame can be expanded and inspected to see the internal state at the various points in the stack trace. Between that renderer, the heavy usage of `django-debug-toolbar`, which ships with a template context inspector, and my preference throwing `pdb` everywhere, there is a notable lack of a good `repr()` experience in much of Django, both in debugging public API (that is, the bits a user will use and encounter), and internals that might be exposed, or could otherwise be served better by having a repr that says something more than it's address/id. A couple of previous tickets have addressed this in minor, one off ways - #23167, #22906, #22531 - but as I've begun collecting places they could supply useful info as I spot them in my stuff, they've become a hodgepodge across a number of modules. For example, a couple I've got implemented: {{{ }}} All of which, IMHO, provide a more useful context in which to evaluate state. The branch I have implemented my reprs in is in no way merge ready yet, partially because there's no tests, and it'd need rebasing & squashing, but also because there are some parts I'd like to see reprs on but haven't landed on a good way to do so. An example being the concept of a `Loader`, which currently has no repr() and thus shows up as `` which at least tells us which loader is being referenced. Given the convention so far for reprs() is just the class name (rather than module + class), the fact all Loaders (and now Engines) all share the same class name means in exposing more useful internal state we lose knowledge of the loader in question's module namespace. As I write this, I've got at least rudimentary (as in, it was possibly to replace the 0x... with at least one object-state variable) reprs for: * ~~`StaticNode`~~ added in e6406853c326ea9210d07766138d2b193c6d1fba * ~~`BlockTranslateNode`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141 * ~~`URLNode`~~ added in d3ecef26b9fda02b88f925a800ae38dd5873c878 * ~~`Token`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668 * ~~`Lexer`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668 * ~~`Parser`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668 * ~~`FilterExpression`~~ added in 179ee13eb37348cd87169a198aec18fedccc8668 * ~~`MiddlewareMixin`, `RedirectFallbackMiddleware`, `MessageMiddleware`, `RemoteUserMiddleware`, `CsrfViewMiddleware`~~ added in dc86a25a677d05703e0bb021b178e44412cea7e9 * ~~`Col`~~ added in 7171bf755b0c4be85ddbcc164eaf87164c131021 * ~~`Lookup`~~ added in d3d95d645fc9f36355d27598475612de43587db1 * ~~`BaseDatabaseWrapper`~~ added in 6fa2930573ff862a7f8ae8a11aa8bb7253fddeb7 * ~~`SQLCompiler`~~ added in 6fa2930573ff862a7f8ae8a11aa8bb7253fddeb7 * ~~`JoinPromoter`~~ added in 6fa2930573ff862a7f8ae8a11aa8bb7253fddeb7 * ~~`HttpResponse`, `HttpResponseRedirect`, `HttpResponseNotAllowed`~~ added in c96f11257baf43188ff9daeddab3221992925c85 * ~~`LazySettings`, `Settings`, and `UserSettingsHolder`~~ added in 9c40f01a66bd15457e10a0bbf28c803968b5dabb * ~~`GeoIP2`~~ added in d4b10a725614322769a419180039771634a06571 * ~~`PermWrapper`~~ added in 22da686ca93e99f8091334f66d7199bc29b85c83 * ~~`BaseStorage`~~ added in 7dd502b0e1e7d3e7fa2c5a2d54bbc926dbcf5f92 * ~~`ChangeList`~~ added in 7dd502b0e1e7d3e7fa2c5a2d54bbc926dbcf5f92 * ~~`AdminForm`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141 * ~~`SimpleTemplateResponse`~~ added in c96f11257baf43188ff9daeddab3221992925c85 * ~~`TemplateResponse`~~ added in c96f11257baf43188ff9daeddab3221992925c85 * ~~`AdminSite`~~ added in e4da3654367cd5f5c06ab109ece0042631faaa02 * ~~`ModelAdmin`~~ added in e4da3654367cd5f5c06ab109ece0042631faaa02 * ~~`Origin`~~ added in 4f4f770f77c5d720484c0a71f6a19b9affcc7e28 * ~~`Template`~~ added in 4f4f770f77c5d720484c0a71f6a19b9affcc7e28 * ~~`BlockContext`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141 * ~~`IncludeNode`~~ added in 66ed03e7c9ae4cd754aa918c6f4c9227cf424141 * ~~`Engine`~~ added in c609d5149c9295207cd7b2e8154e7b80a18d834a * ~~`OrderedSet`~~ added in afb0eb8bb3e1c6f7ea842d2cede684eb4aec3f3d * ~~`StreamingHttpResponse`~~ added in bbb3965826c91406b94b819af7315ea1d39ec217 If accepted, this ticket could just track whatever I can end up getting reviewed/merged, or it could be a meta-ticket for accepting as a principle, and I could spin off tickets for more targeted areas. ",New feature,closed,Core (Other),dev,Normal,fixed,,django@…,Accepted,0,0,0,0,1,0