> My question: I understand that core dumping by the Python interpreter is > normally considered a bug -- one that should be reported on SF -- and > fixed. But does that principle apply to this sort of use (or probably > abuse) of the new module. In other words, does the 'no core dump' > contract > include a 'byte code compiled by the interpreter' proviso. Or is ceval > intended to be robust against random strings masquerading as valid byte > code (which would seem require an InvalidByteCode exception). Or in still > other words, is there a bug that I should encourage reporting of, or is > 'don't do that' the extent of a proper response? > > Terry J. Reedy File the bug report and assign to me. Raymond
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4