Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2000-April/003525.html below:

Arbitrary attributes on funcs and methods)

• Previous message: [Python-Dev] Object customization (was: Arbitrary attributes on funcs and methods)
• Next message: [Python-Dev] Object customization (was: Arbitrary attributes on funcs and methods)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> I think that we get 95% of the benefit without any of the
> "dangers"
> (though I don't agree with the arguments against) if we allow the
> attachment of properties only at compile time and
> disallow mutation of
> them at runtime.

AFAIK, this would be a pretty serious change.  The compiler just
generates (basically)PyObject_SetAttr() calls.  There is no way in
the current runtime to differentiate between "compile time" and
"runtime" attribute references...  If this was done, it would simply
be ugly hacks to support what can only be described as unpythonic in
the first place!

[Unless of course Im missing something...]

Mark.

• Previous message: [Python-Dev] Object customization (was: Arbitrary attributes on funcs and methods)
• Next message: [Python-Dev] Object customization (was: Arbitrary attributes on funcs and methods)
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4