> The web devs tell me that fuckit's versioning scheme is confusing, and that I should use "Semitic Versioning" instead. So starting with fuckit version ה.ג.א, package versions will use Hebrew Numerals.

Heh.

There was a (proposed? I don't remember) library or language that deleted source lines that caused errors. Repeated invocations would eventually yield source that did not produce any errors. Of course, it might be an empty file...

Is this essentially "On Error Resume Next" for Python?

[0] https://msdn.microsoft.com/en-us/library/aa266173(v=vs.60).a...

"On Error Resume Next specifies that when a run-time error occurs, control goes to the statement immediately following the statement where the error occurred where execution continues. Use this form rather than On Error GoTo when accessing objects."

This brings me maniacal joy :D. One time, I had to make the opposite functionality: a streaming module was eating all errors inside a while True loop. This was making debugging really aggravating. So I made a DieWithHonor exception that caused the program to call process.kill() on its own PID >:D

Absolute child's play compared to:

https://gist.github.com/llllllllll/b1ac68a6b77535a64c0b13bfd...

(Python's LOAD_FAST bytecode does `fastlocals[i]`: how can we abuse the lack of bounds checking on this array access?)

(We've also discussed potential extensions this to approach "lift" C-extension code in bytestrings into interpreter objects. This would be useful to escalate existing interpreter attacks in environments that try to lock things down.)