Context Navigation

Changes between Initial Version and Version 1 of Ticket #25912, comment 10

-              initial
+              v1
 I am not opposing the patch, but I do wish that we think what operations we want to expose on F() *before* we commit this one. The choices seem to be:
 ) bitand() and bitor() to expressions
+) Move bitand() and bitor() to expressions
 ) Add bit shift methods, but stop there
 ) All methods welcome to F()
+) Allow addition of other methods, too
 I don't like 3), as that means Django core is controlling the list of official F-methods.  If users were able to add their own methods to F (AKA callable transforms), then I wouldn't have a problem with 3).