(Sorry Ramiro, I think I replied directly to you instead of to the group. Resending here)
Understood. I believed I was adding a testcase and expanding the scope of the issue but it is certainly possible that they are two separate causes. I will keep that in mind in the future and will certainly open a new issue/revert this one here if everyone would prefer. For what it is worth I was able to reproduce the exception using the original reporter's code but only if I follow the process I outlined in my report. I am still unsure as to what the correct behavior for Django in this situation should be. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
