pite-stubs — type stubs for Pite
Type stubs (PEP 561) for the pite Python module, which the
Pite game engine embeds in its own
CPython interpreter.
The distribution is named pite-stubs because PyPI rejects pite as too
similar to existing projects. The import name is still pite: it is the
engine's native module, so pip install pite-stubs gives your editor types
for import pite.
The module is native (registered from Rust via PyO3), so it is not
importable from a normal Python environment. This package exists purely so
editors and type checkers — Pylance/Pyright — resolve import pite and offer
autocompletion and diagnostics when you work on a Pite project outside the
built-in editor.
Install
pip install pite-stubs
Add it to your project's development dependencies, not to the game's runtime
dependencies: scripts always execute inside the engine (pite edit,
pite run), never in the venv where the stubs are installed.
What you get
import pite
class Player(pite.Node2D):
hud = pite.child("HUD") # resolved lazily to a Node at access time
hit = pite.signal(int)
def _ready(self) -> None:
self.hit.connect(self._on_hit)
def _process(self, delta: float) -> None:
self.position += pite.Vec2(1.0, 0.0)
def _on_hit(self, amount: int) -> None:
self.hud.get_node("../ScoreLabel").text = f"Score: {amount}"
Every node class, property, method, and free function from the engine's schema
is covered. Signal payloads are typed through pite.signal(...), and
pite.child(...) / pite.node(...) resolve to Node through descriptor
typing.
Runtime behaviour
import pite raises ImportError in a normal interpreter, with a message
pointing back at the engine. That is intentional: the name belongs to the
engine's native module, and failing loudly beats an empty module that silently
does nothing.
License
MIT OR Apache-2.0, matching the engine.
Metadata
Release files for pite-stubs 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pite_stubs-0.4.0.tar.gz | 8.1 kB | With provenance | Details for pite_stubs-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pite_stubs-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for pite_stubs-0.4.0-py3-none-any.whl |
Total release size: 17.5 kB
Release files / pite_stubs-0.4.0.tar.gz
| Download URL | pite_stubs-0.4.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c91478ee8ed1453ed3e6ae0288fa21a694d4483b593e49a8a655a2059a6d1e7f
|
|
BLAKE2b-256 checksum How to use checksums |
67230385be0c522b2d8932c925eb9001c03e81f66f17053203859468db3e0961
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / pite_stubs-0.4.0-py3-none-any.whl
| Download URL | pite_stubs-0.4.0-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
527b89be6e5c904740679c29e23c009b53505041ad9f10e3b2b57b7620a8e23f
|
|
BLAKE2b-256 checksum How to use checksums |
f582bde3cbbc6923ca93538ddc2abe3e62e4d0562f548b5a59324134a4482f12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for pite-stubs 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pite_stubs-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.