Changes between Initial Version and Version 1 of Ticket #24251, comment 5


Ignore:
Timestamp:
02/03/2015 09:01:02 AM (7 years ago)
Author:
Steve Jalim
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #24251, comment 5

    initial v1  
    1 @MarkusH - Would this work? -> If #24075 was fixed primarily to aid the development of Django itself (and I'm happy to be corrected on that), would it be viable to park those (stopgap/temporary) changes behind a 'private' (as in private API-style, but still documented) feature flag? Then anyone hacking on Django who hits it can enable it, and everyone else who is building on Django don't get affected?
     1@MarkusH - Would this work? :
     2
     3If #24075 was fixed primarily to aid the development of Django itself (and I'm happy to be corrected on that), would it be viable to park those (stopgap/temporary) changes behind a 'private' feature flag (as in private API-style, but still documented)?
     4
     5Then anyone hacking on Django who hits it can enable it, and everyone else who is building on Django doesn't get affected?
Back to Top