How m1nquan/pytodynamic works
PTD Engine turns a Python script into a Windows DLL exposing a C ABI; hosts then initialize the embedded runtime and invoke exported Python callables. PTD Studio offers a graphical build and verification workflow. The README documents the broader compiler and inspection capabilities, while excerpts confirm Studio’s call into the engine and parts of runtime invocation; unsampled internals are represented only where documented.
Main entry points: ptd_gui.py Studio interface · ptd.py CLI entry
Components 15
Build engine
- CLI entry
ptd.py - SDK discovery
ptd.py - Payload envelope
ptd.py - Native compiler
ptd.py
DLL runtime
- C-ABI exports
ptd.py - Runtime lifecycle
ptd.py - Callable invocation
ptd.py
PTD Studio
- Studio interface
ptd_gui.py - Build workflow
ptd_gui.py - Environment diagnostics
ptd_gui.py - PE / ABI inspector
ptd_gui.py - Verification matrix
ptd_gui.py
Other components
- Developer
- C++ toolchain
- CPython SDK
Connections 16
- Developer → CLI entry: runs CLI
Readme.md - CLI entry → SDK discovery: selects SDK
Readme.md - CLI entry → Payload envelope: packages bytecode
Readme.md - CLI entry → Native compiler: builds DLL
Readme.md - Native compiler → C++ toolchain: uses compiler
Readme.md - SDK discovery → CPython SDK: locates SDK
Readme.md - Developer → Studio interface: uses workstation
Readme.md - Studio interface → Build workflow: configures build
Readme.md - Build workflow → CLI entry: calls compile_engine
ptd_gui.py - Studio interface → Environment diagnostics: shows diagnostics
ptd_gui.py - Studio interface → PE / ABI inspector: inspects exports
Readme.md - Studio interface → Verification matrix: runs verification
ptd_gui.py - C-ABI exports → Runtime lifecycle: exposes lifecycle
Readme.md - C-ABI exports → Callable invocation: exposes calls
Readme.md - Runtime lifecycle → Callable invocation: gates invocation
Readme.md - Callable invocation → Payload envelope: loads payload
ptd.py