Here's to the coming hardware revolution!
He implied it by saying that code is data in Python. Being able to inspect code is not the equivalent.
It is also incorrect to refer to Scheme and Lisp as just dynamic interpreted languages; while they are dynamic and tend to have an interpreter they have also had compilers for quite some time if not from near the very beginning (1957 according to this http://www.softwarepreservation.org/projects/LISP/ibm/Blair-...).
Python doesn't feel to me like revenge of Lisp. It's more like having a shard of a powerful magic artefact; it has some power, but a whole artefact has qualitatively more.
The 8086 was a 16-bit CPU, but you are correct that Lisp didn't run well on it.
Programmatically they were still 16-bit. But as an OS engineer, the 8-bit bus was very much evident when writing drivers, moving data, initializing memory etc.
For cases where DOS had used an instruction that would change, Intel rolled over and crippled that instruction in 16-bit machines (at least for a while) so it would behave the same.
See Hackers, by Steven Levy, also some stuff in Wikipedia
https://en.wikipedia.org/wiki/Lisp_Machines
https://en.wikipedia.org/wiki/Symbolics
Had a summer job doing UI work on a Symbolics machine at MITRE, which was kind of like working in the future in summer of 1985... object oriented development, megapixel WIMP interface. I don't think Sun came close to that until UIM/X, Motif, PowerBuilder in early 90s, Visual C++, VB on PCs...like a 10-year head start.
But python especially feels like the revenge of Scheme and Lisp in the sense of being the same sort of dynamic interpreted language and environment where code is data, all the data and code (including libraries) are very accessible and amenable to inspection and tweaking.