Paul Moore added the comment: > This doesn't work when COM objects have to be kept around. In the AMSI case...
OK, so that's a limitation. Is there any *other* use case for keeping COM objects (that are created by the core) around? If not, then like it or not, this is a problem for AMSI, not for a general "initialise COM" proposal. Basically, I'm saying that it's only worth splitting this proposal out from the AMSI one if there's a benefit (to offset the costs) for code other than AMSI. And there seems to be no such use case. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27417> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
