Changes between Version 1 and Version 2 of Ticket #30536, comment 1


Ignore:
Timestamp:
Jun 2, 2019, 5:26:29 AM (6 years ago)
Author:
pascal chambon

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #30536, comment 1

    v1 v2  
    22
    33Note that the name "DJANGO_SETUP_CALLABLE" may not be optimal, but just "SETUP_CALLABLE" sounded waaaayyy too generic imho, since tons of things are setup in Django during initialization...
     4
     5Maybe it'd be better to immediately call it DJANGO_SETUP_CALLABLES, and allow a list of dotted-strings too, since in the end there will surely be need for multiple presetups (eg mockups for django, mockups for a cms....), let's not force the user to define his own callable just to call several external setup funcs ? Why do people think about it ?
Back to Top