Hi Michał, The bug got accepted by a core dev, so the next thing to do for you if you want to get this bug fixed is probably to work on a patch. With 1.5 coming this year it would be the perfect time to fix it ;) Our plans are obviously to fix all existing bugs, but as you can imagine our time is limited and as such we can't tackle every bug in a timely manner.
Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/ghUQBlIPZeYJ. 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.
