The use of *args also seems like it will be a barrier/just messy if/ when schema evolution ever gets(or with 3rd party apps), I'm +1 on this.
On Jan 29, 8:01 pm, "Russell Keith-Magee" <[EMAIL PROTECTED]> wrote: > On Jan 30, 2008 8:57 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > > > > There should be one-- and preferably only one --obvious way to do it. > > ... > > > On top of that, as I keep saying, it leads to brittle code -- I've > > been bitten a number of times. > ... > > Relying on the order of fields in the model definition is asking for a > > heaping load of fail. Hence my desire to see it go away. > > I'm +1 on removing __init__(*args), for exactly the same reasons. I > can see the use case for handling user-instantaition of models from > custom queries, but I agree with Jacob that the right solution is to > make a clean API interface for this use case, not to open an API entry > point that is inherently prone to bugs. > > Yours, > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
