Hi Collin, On Sat, Aug 23, 2014 at 1:35 AM, Collin Anderson <[email protected]> wrote:
> I like the direction the API is heading. > > RE: composite fields: > Would it help to have an attribute on the individual fields like: > field.parent = TheCompositeField()? This might help determine which fields > to pass into __init__(), and might help when serializing. > > RE: related objects: > I'm interested in doing a djangocon.us sprint to determine the > feasibility of turning related objects into actual virtual fields. > > Both of these issues relate to Michal Petrucha's (koniiiik) Composite Field work, which has been the subject of a couple of GSoC projects. As I understand it, the issues you've described have all been resolved in that branch; as Anssi said in a previous thread, it's mostly ready to go, and would have been in 1.7, except for some interesting interactions with migrations. If you want to contribute, getting that branch, getting it up to speed with the current master, and taking it for a spin would be a great help. The relevant Github repositories are: https://github.com/koniiiik/django/tree/soc2013/composite-fields https://github.com/koniiiik/django/tree/soc2013/foreignkey-refactor I don't remember if they're completely independent, or if one depends on the other; you'll need to dig up the django-dev discussions from last year (or bug Michal on IRC :-) to confirm their current state and usage instructions. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq849myS%2BwmQq-5K7S_YJCvUcFQaRcO7k8%3DoYZido2N_KoGg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
