Why it ships compiled

tCode ships as a compiled package rather than plain Python source. Beyond its two smallest entry-point files, which carry no meaningful logic of their own, everything is built as a native extension specific to your Python version and operating system.

This is a distribution choice, not something that changes how you install or run it day to day: pip resolves and installs the correct pre-built package automatically, exactly like installing any other package. The practical difference only shows up if you go looking for the source afterward, there is no separate, inspectable source distribution the way a pure-Python package would ship.

One consequence worth knowing: because it is published per Python version, 3.9 through 3.14, upgrading your system's Python to a new minor version can mean reinstalling tCode into that new environment, the same as any other compiled package, rather than it simply continuing to work unmodified.

The two small files that do ship as plain source, an __init__.py and a __main__.py, carry no real logic of their own; they exist purely as thin entry points that hand off to the compiled implementation, so reading them tells you essentially nothing about how tCode actually works internally.

This is a distribution decision made once at build time, not something that varies release to release or that you can opt out of by installing differently; every published version of tCode on PyPI ships this way.