On 4/25/07, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> ... If we insist that built-in types are immutable ... They
> could write things like
> class MyFloat(float, DivisionRing): pass
> but this would be fairly painful.
Worse than that once you get 3rd parties involved.
try:
from gmpy import mpf
except ImportError:
class mpf(object): pass
class MyFloat(float, DivisionRing, gmpy): pass
# err ... will this even work at all, with two concrete types?
> On 4/25/07, Jeffrey Yasskin <[EMAIL PROTECTED]> wrote:
> > will seeing "Ring"
> > in a list of superclasses be enough to confuse people?
Yes. That is part of the problem with twisted -- there are so many
layers of abstraction that it takes a while to find something. If
users ever see "Ring" outside of a footnote or the advanced math
section, then something went wrong.
-jJ
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
