I'm coming back to you about one of the first topics we discussed together a few years back.
For you, it is important to have cumulate_progress = True because of the nature of the tasks you're using.
So you decided to set cumulate_progress = True by default when creating a TaskModel object.
for me, it is the contrary, it is important to have cumulate_progress = False because of the nature of the tasks I'm using.
In most application, it will be either one way, or the other, but very rarely both ways in the same application.
What would you say about introducing a constant in the app.settings where we could define DEFAULT_TASK_CUMULATE_PROGRESS to be either True or False
in order to keep retrocompatibility, we could have cumulate_progress = settings.DEFAULT_TASK_CUMULATE_PROGRESS or True if there is no DEFAULT_TASK_CUMULATE_PROGRESS in settings.py
we would also use this as the default value for ProcessInfo.cumulate2parents
Hi Jedie,
I'm coming back to you about one of the first topics we discussed together a few years back.
For you, it is important to have
cumulate_progress = Truebecause of the nature of the tasks you're using. So you decided to setcumulate_progress = Trueby default when creating aTaskModelobject.for me, it is the contrary, it is important to have
cumulate_progress = Falsebecause of the nature of the tasks I'm using.In most application, it will be either one way, or the other, but very rarely both ways in the same application.
What would you say about introducing a constant in the app.settings where we could define
DEFAULT_TASK_CUMULATE_PROGRESSto be eitherTrueorFalsein order to keep retrocompatibility, we could have
cumulate_progress = settings.DEFAULT_TASK_CUMULATE_PROGRESSorTrueif there is noDEFAULT_TASK_CUMULATE_PROGRESSinsettings.pywe would also use this as the default value for
ProcessInfo.cumulate2parentsWould that be something ok for you ?