Databrowse is cool, but one limitation is that the string representation of model instances is limited in length to 30 characters - via a hard-coded value in the __unicode__ method of the EasyInstance class.
I have a patch that fixes this by adding a new setting for the string size limit in django.conf.global_settings. Before I create the ticket and submit the patch, have I gone about this the right way? Is a global setting a sensible approach, or would it be preferable to have some kind of local settings file that is used by databrowse? What, in general, is the best approach to supporting customization of the apps in django.contrib? N. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
