slopfront
preferences

Why does python has a middle layer of creating bytecode?

0 points · submitted 2d ago by u/DueBid3298 · Discussion

  1. Is bytecode platform-specific, and why?
  2. What does bytecode look like?
  3. What is the difference between a C++ executable file produced after compilation and what a Python VM produces?
  4. What does the Python VM actually produce? Is it a binary, CPU instructions, or something else?
  5. What is the difference between a binary, an executable, and a CPU instruction? Explain from the basics in detail with specific examples.

9 comments · 17% upvoted · other discussions

comments

B3d3vtvng69 28 points · 2d ago

This is not the place to upload your homework lmao. You’re one google search away btw…

abs0lute888 9 points · 2d ago

honestly props to OP for going an extra mile and posting on reddit instead of using AI lol

B3d3vtvng69 1 points · 2d ago

fair enough lmao

stumpylog 9 points · 2d ago

I swear this basic question was just asked, maybe yesterday too

JanEric1 7 points · 2d ago

19 hours ago by the same OP in the learnpython sub https://www.reddit.com/r/learnpython/comments/1xfeagc/why_do_we_need_cpython_and_python_virtual_machine/

metaphorm 2 points · 2d ago

the python interpreter uses its own specific runtime specification, and bytecodes are produced by interpreting Python code into machine code for this specification. the actual python distribution installed on the host machine has the interfaces that translate python bytecode into machine executable native code. this is why you have to installed the correct python distribution for your machine architecture.

Beard_o_Bees 1 points · 2d ago

Seems like this should be pinned at the top of the sub.

Sad_Speaker824 1 points · 18h ago

I think of bytecode as instructions for the Python VM rather than the CPU, so it works across platforms but is tied to the Python version, and the .pyc cache just saves re-parsing your source, whereas a C++ build produces machine code for one specific CPU.