Sebastian F wrote: > Another issue was with "BooleanFields". I noticed they always hit the > history even if not changed. Someone else had noticed this too and > already posted a ticket (http://code.djangoproject.com/ticket/1511). > Pretty easy to fix but has been open for 4 months? > > These are very small fixes/enchantments but still kind of frustrating > to apply them yourself after updating django. So my question is, what > is the reason to ignore this kind of tickets? > If you've patched this code in your install why don't you submit the patch to Trac so the developers can review it and possibly get the fix in the next release? Be pro-active and help the community. The sooner patches get into these bugs (especially if they're easy) the sooner they'll get closed.
Jay --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
