Antoine Pitrou added the comment: > 1) the mro tuple in the type object is "nerfed" to contain a > Py_None reference in its first place
I like the idea, but I find the implementation (the new macros) quite convoluted. I think special-casing the first tuple element where necessary would be cleaner. > 2) the descriptors are modified to hold a weak-reference to the target > type, rather than a strong reference. What would happen if someone keeps a reference to the descriptor and not to the class object? Is it a possible use case? > 3) Fix process cleanup. This was already done in changeset 6f4627a65c0a. You might want to update your working copy. Does your patch cater to all possible implicit cycles, or only a subset of them? ---------- nosy: +amaury.forgeotdarc, pitrou _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17950> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
