PYO3-INTROSPECTION(1)

πŸ“¦ version 0.29.3, in epel 10, epel 9, fedora 43, fedora 44

πŸ’– PYO3-INTROSPECTION πŸ’–

okay bestie, so this is a page from the User Commands corner of the manual, and the command is pyo3-introspection. And like… the name is literally the whole personality: it introspects a Python cdylib built using PyO3 and generates type stubs. That's it, that's the job. It looks inside your compiled library, figures out what's in there, and hands you back .pyi-style stub files so your editor stops screaming at you. iconic behaviour honestly 🌈✨


✨ SYNOPSIS ✨

pyo3-introspection binary python_module stub_path

that's the whole vibe. three little arguments, in that exact order, no cap. πŸŽ€


πŸ’… OPTIONS πŸ’…

🫢 POSITIONAL ARGUMENTS

so these aren't like flags flags, they're positional β€” meaning the order is the whole point. You can't shuffle them. The command reads them left to right like a group chat you're catching up on. πŸ’€

  • binary β€” the Path of the binary to introspect. Give it the actual binary you want it to go snooping through. πŸ¦‹
  • python_module β€” the Name of the python module to introspect. This is the module name, not a path. Just the name, bestie. πŸ‘‘
  • stub_path β€” the Path of the directory to write the stub to. Note that it's a directory, not a file β€” it's gonna drop the generated stub in there. πŸ“βœ¨

fr fr: three args, exact order, and stub_path is a directory. That's the entire interface. No sneaky extra flags hiding in here. πŸ™ˆ

and that's the page!! short, sweet, and it does exactly one thing but it does it flawlessly. This little slice of documentation was served up July 2026 β€” so if you're reading this from the future, hi, hope the stubs are still slaying. πŸ’œπŸ’…

later bestie, go generate some stubs 🫢🌸

πŸ“¦ where this page comes from