Terry Reedy wrote:
> "Bruno Desthuilliers" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> Terry Reedy wrote:
>>> "Bruno Desthuilliers" <[EMAIL PROTECTED]> wrote in message
>>> news:[EMAIL PROTECTED]
>>>> The current namespace object, of course.
>>> Implementing a namespace as a Python object (ie, dict) is completely
>>> optional and implementation dependent. For CPython, the local namespace
>>> of
>>> a function is generally *not* done that way.
>> I know this, and that's not the point here. The op's question seemed to
>> imply that the hypothetical __assign__ method should belong to the rhs
>> object, which is obviously not the case - it must of course belongs to
>> the lhs 'object'.
>
> And my point is that in general there is no lhs object for the method to
> belong to.
<nitpicking>
Mmm... Of course, there's always something that's being used as a
namespace. But yes, this something may not be directly accessible as a
Python object.
</nitpicking>.
--
bruno desthuilliers
python -c "print '@'.join(['.'.join([w[::-1] for w in p.split('.')]) for
p in '[EMAIL PROTECTED]'.split('@')])"
--
http://mail.python.org/mailman/listinfo/python-list
