Issue34314
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2018-08-02 03:02 by bup, last changed 2022-04-11 14:59 by admin. This issue is now closed.
Messages (3) | |||
---|---|---|---|
msg322907 - (view) | Author: Dan Snider (bup) * | Date: 2018-08-02 03:02 | |
Right now, you really gotta jump through hoops in some cases if you only want to use __new__ and don't care about __init__ (is there ever a time where you'd use both?). The problem originates in type.__call__. I'm attaching a full Python implementation of type_call/object_init at the end, but here's a tl;dr representation of the issue i type_call (where the whole thing can be basically summarized as this): def type_call(type, *args, **kws): r = type.__new__(type, *args, **kws) if not issubclass(r, type): type(r).__init__(r, *args, **kws) return r So if type(r).__init__ is object.__init__ or some other method with an incompatible signature to the metaclass's, errors are raised, which leads to having to implement really annoying workarounds. The annoyingness is compounded further by the fact that all object_init does is make sure it didn't receive any arguments. All of that can be avoided by setting __init__ in the class to None, which would have the same effect as setting tp_init to NULL on an extension type. Perhaps with a caveat that the only current reachable __init__ is object.__init__? I don't really find myself in situations involving the need for __new__ too often, but wouldn't this have a profoundly positive impact on pickle as well? One thing I can think of is there can be a universal pickle implementation for extension types with Py_TPFLAGS_BASETYPE set and a nonzero dict offset since if it detected a NULL init all it has to do is memcpy the base struct and pickle the instance dict. Anyway, the C code is pretty easy to understand but here's a Python implementation almost exactly equivalent that shows a case where a metaclass can be used as a callable that accepts an arbitrary number of arguments instead of a forced three and returns a class: PyType_Type = type Py_TYPE = type PyType_IsSubtype = issubclass PyTuple_Check = tuple.__instancecheck__ PyDict_Check = dict.__instancecheck__ PyDict_GET_SIZE = dict.__len__ PyTUple_GET_SIZE = tuple.__len__ NULL = 0 ALLOW_NULL_INIT = False def excess_args(args, kws): return args or kws class Object: def __init__(self, *args, **kws): # object_init literally does nothing but check for zero len args/kws # (bit of a tangent but why is excess_args not a macro...?) if ALLOW_NULL_INIT: return tp = Py_TYPE(self) print('Object.__init__, type is:', tp.__name__) if excess_args(args, kws): if tp.__init__ is object.__init__: raise TypeError("object.__init__() takes no arguments") raise TypeError(f'{tp.__name__}.__init__() takes no arguments') def fake_init(*args, **kws): pass class Type(type): def __getattribute__(self, attr): value = type.__getattribute__(self, attr) if attr == '__init__': if ALLOW_NULL_INIT and value is None: return fake_init return super(type(self).__mro__[1], self).__init__ return value def __call__(tp, *args, **kws): if getattr(tp, '__new__', 0) == NULL: raise TypeError(f"cannot create {tp.__name__} instances") obj = tp.__new__(tp, *args, **kws) if (tp is type and PyTuple_Check(args) and PyTuple_GET_SIZE(args)== 1 and (kws == NULL or (PyDict_Check(kws) and PyDict_GET_SIZE(kws)==0))): return obj if not PyType_IsSubtype(Py_TYPE(obj), tp): return obj tp = Py_TYPE(obj) # Here's where the problem is. What could possibly be negatively # affected by this? if getattr(tp, '__init__', 0): res = tp.__init__(obj, *args, **kws) return obj def autoname(arg): return '_'.join(arg.split()) def autobase(opt): return () if not opt else (opt,) class MetaBase(Object, type): pass class Mixin1: pass class Meta(MetaBase, metaclass=Type): __init__ = None def __new__(metacls, name, opt=None): return super().__new__(metacls, autoname(name), autobase(opt), {}) if __name__ == '__main__': try: foobar = Meta('foo bar', Mixin1) except TypeError as er: print(f'could not make foobar because: {er}') print('setting ALLOW_NULL_INIT to True;') ALLOW_NULL_INIT = True foobar = Meta('foo bar', Mixin1) print('foobar.__name__ is:', foobar.__name__) print('foobar__mro__ is:', foobar.__mro__) |
|||
msg322908 - (view) | Author: Raymond Hettinger (rhettinger) * | Date: 2018-08-02 03:17 | |
> Right now, you really gotta jump through hoops > in some cases if you only want to use __new__ > and don't care about __init__ I'm now sure I see the difficulty. It is easy to define a classes with __new__ and without __init__: >>> class A: def __new__(cls, *args): print('New called with', cls, 'and', args) return object.__new__(cls) >>> a = A(10, 20, 30) New called with <class '__main__.A'> and (10, 20, 30) >>> isinstance(a, A) True > Like __hash__, allow setting MyClass.__init__ to None FWIW, the API for hashing being set-to-None wasn't done because we like it (there a numerous downsides). It was done because we needed hashing to be on by default and there needed to be a way to turn it off. The downsides are that it confuses users, it is hard to teach and remember, and it adds a branch to various APIs which would then need to test for None. Instead, we prefer the pattern of having object() provide a default dummy method that either does nothing or gives up (like object.__init__ or the various rich comparison methods for object). This simplifies downstream code than doesn't have to check for a rare special case. |
|||
msg322909 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) * | Date: 2018-08-02 03:37 | |
Setting __hash__ to None doesn't do what you think. It doesn't prevent __hash__ from being called by hash(), instead it produces a TypeError. >>> class A: __hash__ = None ... >>> hash(A()) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: unhashable type: 'A' Actually the effect of special casing __hash__ is not raising a TypeError, but raising a TypeError with better error message. A TypeError was already raised before if set __hash__ to a non-callable. In 2.7: >>> class A: __hash__ = None ... >>> hash(A()) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: 'NoneType' object is not callable If you want to prevent an inherited __init__ from being called by types's __call__, you can define an __init__ with an empty body. def __init__(self, *args, **kwargs): pass |
History | |||
---|---|---|---|
Date | User | Action | Args |
2022-04-11 14:59:04 | admin | set | github: 78495 |
2018-08-03 06:53:02 | rhettinger | set | status: open -> closed resolution: rejected stage: resolved |
2018-08-02 03:37:07 | serhiy.storchaka | set | nosy:
+ serhiy.storchaka messages: + msg322909 |
2018-08-02 03:17:08 | rhettinger | set | assignee: rhettinger messages: + msg322908 nosy: + rhettinger |
2018-08-02 03:02:06 | bup | create |