James Bennett - A Bit about Bytes: Understanding Python Bytecode - PyCon 2018
HTML-код
- Опубликовано: 12 май 2018
- Speaker: James Bennett
At some point every Python programmer sees Python bytecode files -- they're those '.pyc' files Python likes to leave behind after it runs. But have you ever wondered what's really going on in those files? Well, wonder no more! In this talk you'll learn what Python bytecode is and how it's used to execute your code, as well as how to decipher and read it, and how to reason about bytecode to understand the performance of your Python code.
Slides can be found at: speakerdeck.com/pycon2018 and github.com/PyCon/2018-slides
I could listen to this guy all day. what a great speaker and teacher!
great talk & speaker
Fantastic talk! Was looking for a good explanation of Python bytecode, and this was absolutely perfect.
Excellent talk. Thanks for uploading.
Damn good. Thanks for sharing your knowledge!!
Excellent: clear, concise.
Many thanks for uploading this. Really informative and excellent presentation.
Very interesting talk! Thanks!
Fantastic talk
that was great, thankyou!
Great talk and Idea on Bytecode Thanks.
No Slides available in the links provided
genial
Great talk....
Now i take care about byte code size while developing in python......haha..
0:36 that sounded like a cult
Even funnier and weirder is that the slide that follows when he is talking about the the clarity and clearness of Python isn't Python but a disassembly of Python bytecode which isn't so clear or readable. The dis module output can be cryptic, incomplete, and requires a talk like this to try to explain what it means.
I could not find the slides at both links you shared
bien
he should make audio books :)
No slides for both links.
Farit Mutugullin Wery good, I will take cary about. Try to understand a bit more about Python virtual machine...
Its a good talk, but feels like adopting this practically seems conflicting with readability of code for humans.
so much narcissism in python community. if you want an easy to read language, go for Ruby :)
fuck off
@@cssensei610 Python and js were mistakes
Says the guy making the only narcissistic comment in the comment section.