On Wed, Oct 18, 2017 at 10:30 PM, Serhiy Storchaka <storch...@gmail.com> wrote:
> 18.10.17 22:21, Koos Zevenhoven пише: > >> Nice! Though I'd really like a general solution that other code can >> easily adopt, even third-party extension libraries. >> > > What is the more general solution? For interrupting C code you need to > check signals manually, either in every loop, or in every iterator. It > seems to me that the number of loops is larger than the number of iterators. > > Sorry, I missed this email earlier. Maybe a macro like Py_MAKE_THIS_LOOP_BREAKABLE_FOR_ME_PLEASE that you could insert wherever you think the code might be spending some time without calling any Python code. One could use it rather carelessly, at least more so than refcounts. Something like the macro you wrote, except that it would take care of the whole thing and not just the counting. -- Koos -- + Koos Zevenhoven + http://twitter.com/k7hoven +
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
