#5505: Self-Referential ForeignKeys broken using newforms form_for_instance 
with a
formfield_callback
-------------------------+--------------------------------------------------
   Reporter:  danlarkin  |                Owner:  nobody         
     Status:  new        |            Component:  django.newforms
    Version:  SVN        |           Resolution:                 
   Keywords:             |                Stage:  Unreviewed     
  Has_patch:  1          |           Needs_docs:  0              
Needs_tests:  0          |   Needs_better_patch:  0              
-------------------------+--------------------------------------------------
Comment (by danlarkin):

 @jkocherhans: I exercised bad form when uploaded the patches, I should
 have been a little more clear with naming them etc.
 
 In the interest of not polluting this ticket with yet more attachments,
 though, I'll just tell you which patches to apply.  '''db-models-fields-
 init.patch''' and '''newforms-forms.patch''' fix the problem (at a cursory
 level, anyway).  '''tests-regressiontests-forms-models.patch''' adds a
 regression test to show off the problem (and fix).  '''newforms-
 deepcopy.patch''' is wrong and useless (I wish I could delete
 attachments!).
 
 @mtredinnick: You are exactly right about !__deepcopy!__.  I don't have
 the level of familiarity with django necessary to know if/how many complex
 structures might end up inside a Field object, so someone else will have
 to take over on that front.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/5505#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to