I'm trying to understand what you're trying to accomplish at a very basic level. I'm not familiar with any of the third-party packages you mentioned. How will the proposed changes in Django simplify them? In your second mail you proposed a "form_business" kwarg with a "YourFormBusiness" argument without a description of what that class looks like. I'm sure I could understand more if I spent a lot of time looking into it, but please try to make it very easy -- you'll get more feedback this way.
p.s. not sure you meant by "FieldBase" -- there is no class in Django by that name. On Monday, February 1, 2016 at 3:38:37 PM UTC-5, is_null wrote: > > Thanks for the advice, I started trying moving form-related stuff from > FieldBase into a new ModelFormFieldBase class, and it turns out that > there's a lot more we could, or should, move than just > value_from_object and save_form_data. > > Why not move out everything that couples the form field and the model > field in from FieldBase into ModelFormFieldBase while we're at it ? > > I like this idea, are you more interrested in seeing a before / after > of 0. just moving value_from_object + save_form_data or 1. moving form > stuff from FieldBase into ModelFormFieldBase ? > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/908759b4-11bd-492b-b4c6-7b667c031292%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
