Local Installation and Python Runtime Configuration
Technical specifications for configuring local environments, installing the LangPy package via PIP, and executing Spanish-native transpiled code blocks.
1. Python Interpreter Verification
LangPy requires Python 3.10 or higher installed on the host operating system to execute lexical transpilation and AST processing.
Verify the presence and version of the active Python runtime using the standard system CLI:
- Windows: python --version
- macOS / Linux: python3 --version
If Python is missing or outdated, install the latest stable version from python.org. On Windows environments, ensuring 'Add Python to PATH' is checked indexes the binary globally.
2. Virtual Environment Setup
Utilizing isolated Python virtual environments (`venv`) isolates dependencies and avoids version conflicts with system-level packages.
Environment Provisioning
Initialize a isolated workspace directory using the standard `venv` module:
- Windows: python -m venv venv
- macOS / Linux: python3 -m venv venv
Activation
Activate the environment context according to the target terminal framework:
- Windows (CMD): venv\Scripts\activate
- Windows (PowerShell): .\venv\Scripts\Activate.ps1
- macOS / Linux: source venv/bin/activate
3. Package Installation via PIP
The official transpiler and runtime hooks are distributed as a standard Python package on PyPI.
pip install langpy
Installing `langpy` embeds the CLI toolchain and lexical mapper required to translate Spanish source constructs directly into valid Python bytecode.
4. Script Execution Mechanics
LangPy recognizes `.pyes` source files containing Spanish syntax definitions.
- Create a standard text file named `main.pyes` within your active workspace.
- Write a native language expression inside the source file:
- Execute the script via the LangPy CLI binary.
imprimir("Hola desde LangPy local")CLI Execution Command
The entry point binary invokes the transpiler engine before handing execution off to the underlying Python VM:
langpy main.pyes
The core engine resolves semantic mapping dynamically without introducing overhead or modifying native CPython execution speed.
Environment Diagnostics & Troubleshooting
Common system setup issues, execution policy restrictions, and environment recovery solutions.
Python or PIP binaries not recognized in PATH
The terminal reports that 'python' or 'pip' is not recognized as an internal or external command.
System environment variables were not automatically updated during installation.
Re-run the official installer, select 'Modify', and ensure 'Add Python to PATH' is explicitly checked.
PowerShell Script Execution Policy Restriction
PowerShell blocks virtual environment activation due to system execution policies.
Default Windows security settings restrict unsigned local script execution.
Grant process-scoped execution privileges by running: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process
Binary 'langpy' not found in path
The CLI tool returns command not found despite package installation.
The virtual environment is inactive or PIP installed the package to a non-indexed directory.
Verify active environment indicators in the prompt, upgrade PIP, and force package reinstallation: python -m pip install --upgrade pip && pip install langpy
Runtime Version Incompatibility
The parser raises syntax or AST exceptions when interpreting standard `.pyes` source files.
The host environment is executing an unsupported CPython version lower than 3.10.
Check the active runtime version with `python --version` and upgrade the environment to Python 3.10 or newer.