On Wed, 2009-01-28 at 23:21 -0800, Vinay Sajip wrote: [...] > I was hoping there was another way. Of course subclassing's not hard > to do, but it means doing it for every field class. I was looking at > moving an application over from SQLAlchemy, which offers this feature > both for models and fields.
That's not very natural Python behaviour, though. You can't expect to pass in extra arbitrary arguments to class constructors for normal Python classes and have them hold onto it for later collection. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
