Message144401
| Author |
ncoghlan |
| Recipients |
alex, belopolsky, jcea, meador.inge, ncoghlan, rfk, rhettinger |
| Date |
2011年09月22日.04:28:04 |
| SpamBayes Score |
7.4579526e-05 |
| Marked as misclassified |
No |
| Message-id |
<1316665685.24.0.0103012336174.issue11816@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
'Op' is just an abbreviation of 'operation'. So 'operation code' becomes 'opcode' and 'operation information' becomes 'opinfo'. The fact that it comes for the 'dis' module gives the context that the *kind* of operation we're talking about is a Python byte code instruction.
When people are hacking on bytecode in the future, they'll likely end up using get_opinfo() a fair bit, so swapping the succinct 'opinfo' for the verbose 'bytecode_instruction' strikes me as a poor trade-off. |
|