STINNER Victor added the comment: > Hm. If the problem is most prominent with 3.3, why mark the issue as 3.6?
Well, I plan to implement this feature in "asyncio", so for 3.3-3.6 in fact. > Do you have an implementation already? Nope, it's more a TODO task for myself :-) > Maybe it can be a 3rd party package rather than integrated in asyncio debug > mode? Hum, I'm not sure. My idea is to add code in Future.set_exception() because I will probably need a reference to the exception object (and maybe to the Future object). Currently, it's not possible to replace the Future class (whereas we have BaseEventLoop.set_task_factory and BaseEventLoop.create_task). I don't think that it's worth to make it possible to replace/hook this class. I don't expect a huge complex code to detect reference cycles. Please give me some weeks to investigate this issue. It will be easier to discuss with a working patch. I opened the issue as a reminder for myself, but also to colaborate on it. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24598> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
