Hi all, I'm looking at r16297 (https://code.djangoproject.com/changeset/16297), and I don't like this approach, I understand what it is trying to accomplish, but it has several downsides that don't appear to have been considered:
a) On CPython a class object is pretty large, and they are very easy to get into reference cycles that won't be collected for a while. b) On PyPy (and IronPython AFAIK, and *maybe* CPython) creating a new class for each instance can lead to poor performance because they prevent reusing various caches, or can cause overspecialization. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
