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


Ignore:
Timestamp:
Dec 14, 2015, 11:46:10 PM (9 years ago)
Author:
Anssi Kääriäinen

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #25912, comment 10

    initial v1  
    66
    77I 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:
    8   1) bitand() and bitor() to expressions
     8  1) Move bitand() and bitor() to expressions
    99  2) Add bit shift methods, but stop there
    10   3) All methods welcome to F()
     10  3) Allow addition of other methods, too
    1111
    1212I 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).
Back to Top