¡Mangle You A Python Interpreter for New Behaviour!
summary
Implements two hacks: quiet_None (a context/decorator that makes None accept calls) using CTypes and sys.getframe, demoed working; question_dot (safe attribute access) implemented by adding a new token/AST node and compiler output in PyPy but the planned source-code‑codec approach to transparently run it on CPython 2.7 fails; changes touch the parser and compiler, leave a stack-value bug, and require toggling via context or custom build. Repos and slides are provided for the partial proofs of concept.
AI-written summary · about
chapters (32)
- 0:00Intro
- 2:14Quiet None
- 3:22callable None
- 5:20quietNone
- 8:31quietNone explanation
- 10:23I wrote this
- 11:17Deconstructing Functional Programming
- 12:00Newspeak
- 13:14None
- 13:36SafeNavigation
- 13:57SafeAttributeAccess
- 14:44len method
- 16:52pep 463
- 20:55middle way
- 21:40partial demo
- 25:05Why I decided not to do it
- 26:59Im not racist
- 27:12Why do you hate python
- 27:34Forward compatible
- 28:00Roast peps
- 28:43lisp envy
- 29:23Javascript
- 30:32Podgill
- 31:41I love Python
- 31:53What could I do
- 32:17Fix the stack problem
- 32:34Get the source codec hack
- 33:31Whats next
- 33:47What Id like to do
- 34:02Time Spent
- 34:42Restartable Exceptions
- 36:49Macropi
related talks
25mPython as a Hackable Language for Interactive Data Science
01h 07mWhat Does It All Really Mean
38mDynamic Code Instrumentation with Hacked Interpreters
49mYou Used Python for What?!
31mDon't Do This
28mHere be dragons: some elegant and ugly hacks in CPython
02h 26mPointers in Python
43m5 Years of Bad Ideas