What is a .PYI file?
.PYI is a Source code & build files file (Data & code). Analyser identifies a .PYI file and reads the metadata in its header, right in your browser.
- Did you know
- A .pyi file is a Python stub holding only type hints - function signatures and types with no actual code.
- Type checkers like mypy and IDEs read .pyi stubs to understand a library's types, even for modules written in C.
- The Typeshed project collects .pyi stubs for the standard library and popular packages.
- What Analyser reads
- Open and read programming-language source, build and configuration files as text: C, C++ and their headers, C#, Java, Kotlin, Go, Rust, Python, Ruby, PHP, Swift, Scala, Lua, Perl, R, Dart, Groovy and Visual Basic, GPU shaders (GLSL, HLSL), shell scripts (sh, Bash, Zsh, Fish), and the build and tooling files that fill a source repository - CMake, Makefiles, Ninja, Autotools (.in / .ac / .am / .m4), qmake projects, Doxygen configs and the dotfiles that configure Git, Docker, npm, ESLint, Prettier, Cursor and clang-format. Also opens Objective-C++ (.mm / .hmm), more GPU shaders (.fs / .vs / .gs), Boost.Jam and Meson build scripts, Unix manual pages, web stylesheets (Less, Sass/SCSS) and Svelte components, gettext translations (.po / .pot), Apple entitlements and licence/readme text, plus Cython (.pyx), OpenGL shaders (.fsh / .vsh / .geom), Git hook samples, ESLint and Yarn configs and ASP.NET (.aspx) pages. Each opens with a source preview, line count and metadata, entirely in your browser.
- Depth of analysis
- .PYI is an identification-grade format: Analyser recognises it from its bytes and decodes the header metadata it carries, rather than opening it in a full viewer. Formats that do get a full viewer are marked "Full" on the formats page.
- Open a .PYI file
- Drag a .PYI file onto the Analyser home page (or tap to pick one). It is identified entirely in your browser - nothing is uploaded, there is no account, and it works offline once installed.