I don't think a doc patch is sufficient to address the problem, and I highly doubt that a warning would be heard by the vast majority. The attention this bug needs is someone to write a patch to fix the code. Looking at the ticket, 4 weeks ago someone suggested some code that *may* fix the problem. If you were to test the change by modifying your local django and validating that the fix works, I'd think that someone would be more likely to step up and make it committable.
Fixing bugs like this takes a lot of work. Someone needs to identify the issue, verify the problem, write a test case to prove it, track down the issue in code, figure out how it might be corrected, test that it works, perhaps write another test, run the test suite, add release notes, and get it reviewed. Every bug in trac competes for this time. If you're able to effectively halve the time needed, that issue becomes a lot more attractive to 'finish'. I'll even put my hand up to try to fix it if you verify that the patch in the ticket from 4 weeks ago works. I don't (yet) have much experience with the admin, but if there is a straight forward fix available, that'll be a good introduction for me. Regards, Josh -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/91ad25c1-8fa9-4487-8e38-afb193ca076f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
