Code

Changes between Initial Version and Version 1 of Ticket #20625, comment 17


Ignore:
Timestamp:
06/28/13 22:43:59 (10 months ago)
Author:
loic84
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #20625, comment 17

    initial v1  
    11To summarize a bit: 
    22 
    3 - The latest patch should cover all concerns raised so far: it handles specialized querysets such as `ValuesQuerySet`, doesn't break pickling, cruft-free methods definitions, sane defaults (no private or magic methods), a mechanism to opt-out or force-in certain methods and it's robust enough to sustain the complete Django test suite while replacing almost 90% of `Manager`'s public API. 
     3- The latest patch should cover all concerns raised so far: it handles specialized querysets such as `ValuesQuerySet`, doesn't break pickling, cruft-free methods definitions, sane defaults (no private or magic methods), a mechanism to opt-out or force-in certain methods and last but not least, it's robust enough to sustain the complete Django test suite while replacing almost 90% of `Manager`'s public API. 
    44 
    55- We settled that deprecating legacy proxy methods is out of scope for this ticket while acknowledging that it's desirable in the long run. We'll open a dedicated ticket once we land this feature.