I have initially created the ticket
https://code.djangoproject.com/ticket/25618 which addressed the bug that
would occur if south migrations somehow ended up being still present in the
migrations module.
According to a report in:
https://code.djangoproject.com/ticket/25618#comment:7, this seem
flag to their settings file and still use their old workflows.
On Tuesday, October 20, 2015 at 1:02:12 AM UTC-4, David Filipovic wrote:
>
> How about making them opt-out instead of opt-in (for instance with a
> --skip-checks flag)? That way anybody who is aware of the fact that chec
cases? e.g (DateField - DateField)
> --> DurationField)
>
> If you can find an appropriate place for this logic to live then I'm all
> for it. ExpressionWrapper is cumbersome, but it's also necessary for user
> based combinations where the base F/Combinable/Expressi
How about making them opt-out instead of opt-in (for instance with a
--skip-checks flag)? That way anybody who is aware of the fact that checks
are being run every time tests are run and is seeking an increase in
performance can choose to opt-out, whereas anybody not aware (or at least
not full
utput_field type (at least in some cases? e.g (DateField - DateField)
--> DurationField) , as opposed to having to use an ExpressionWrapper,
which makes the interface slightly more complicated?
What do you think, Josh?
Best regards,
David Filipovic
On Thursday, October 15, 2015 at 11:
new classes/methods/functions? I couldn't
find anything on this.
Thank you so much. I hope I can contribute and help make django better!
Best regards,
David Filipovic
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contribution
