iiinova — where your digital self keeps evolving

Replies

Chase Million @millionconcepts.com · 20/05/2025

Have you ever started a Python process, realized that you made a mistake, immediately hit Ctrl+C to interrupt it and then waited a surprisingly long time to get the command line back? This delay is caused by a bug in the compiled #Python extension. :thread:

A code block labeled "A Common Bug (in compiled extension modules)." The code shows an attempt to exit a calculation of a large array of random numbers, and then indicates that a Ctrl+C interrupt takes 3.5 seconds to return, rather than returning immediately as is probably the desired and expected behavior.

2157

Chase Million @millionconcepts.com · 20/05/2025

Dr. Zack Weinberg, Research Software Engineer at Million Concepts, has figured out why this happens and explained how to fix it. He described the problem and solution in a talk at #PyConUS last week. research.owlfolio.org/pubs/2025-py...

research.owlfolio.org

Writing Extension Modules to be Interruptible

130

Chase Million @millionconcepts.com · 20/05/2025

The brief summary of the cause is that the interpreter fails to raise KeyboardInterrupt in a timely fashion. But there is no brief summary of the solution. It requires navigating thread safety, managing the GIL, and preventing arbitrary code execution... while not cratering performance!

120