On Thu, Apr 10, 2008 at 1:08 PM, Jeremy Dunck <[EMAIL PROTECTED]> wrote: > I think with field subclassing, descriptors are a good way to add this > sort of thing, but it needn't be backwards imcompatible, because any > get_XXX_display could just translate to model.XXX.display, etc.
Unfortunately, there are still a number of situations where existing code (and most likely will) break. Some of these situations are easily solvable, others *could* be solved easily by doing a bit of weird stuff that would probably flirt too close to "magic", and others aren't solvable at all. I can itemize them if you'd like, but for the sake of brevity, I'll just say that since I did one of these translations already for #5361, I've done a lot of thinking on the subject. -Gul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
