Early and late binding [was Re: what does 'a=b=c=[]' do]

[Devin Jeanpierre]

> If Python was ever 'fixed' to prevent this issue, I'm pretty sure we'd
> see an increase in the number of questions like the OP's.

What makes you so sure? Both models do make sense and are equally
valid, it's just that only one of them is true. Is it just because
people already used to Python would get confused?

-- Devin

On Sat, Dec 24, 2011 at 9:08 AM, alex23 <wuwei23 at gmail.com> wrote:
> On Dec 24, 6:25 pm, Steven D'Aprano <steve
> +comp.lang.pyt... at pearwood.info> wrote:
>> > It's
>> > much harder to figure out what's going wrong with an early-bound
>> > mutable.
>>
>> Only for those who don't understand, or aren't thinking about, Python's
>> object model. The behaviour of early-bound mutables is obvious and clear
>> once you think about it, but it does require you to think about what's
>> going on under the hood, so to speak.
>
> And here we've come full circle to the point of this thread.
>
> If Python was ever 'fixed' to prevent this issue, I'm pretty sure we'd
> see an increase in the number of questions like the OP's.
> --
> http://mail.python.org/mailman/listinfo/python-list