Context Navigation

Changes between Initial Version and Version 1 of Ticket #5863, comment 38

-              initial
+              v1
 @lukeplant, the basic problem you've correctly raised is that list_display allows for callables and hence arbitrary names can be used which are simiar to the syntax for foreign key fields.
 However, this problem exists for list_filter also: someone may define a field with the name class__field and try to use that in list_filter as a foreign key field. (i've just checked that you can indeed name a field like that)
+However, this problem exists for list_filter also: someone may define a field with the name `class__field` and try to use that in list_filter as a foreign key field. (i've just checked that you can indeed name a field like that)
 So we can't really be compensating for dev stupidity at the cost of functionality as we haven't done in list_filter also.
 Since all FKs always start with an alphabet are in the regex format (.+__.+.*), the __unicode etc cases can be easily and correctly filtered as is required to be done in list_filter.
+Since all FKs always start with an alphabet are in the regex format `(.+__.+.*)`, the `__unicode__` etc cases can be easily and correctly filtered as is required to be done in list_filter.