Overview

PyGyat requires minimal configuration to get started. This guide covers the essential configuration settings and customization options available.

File Extensions

• Default file extension: .gyat
• PyGyat recognizes and processes files with .gyat extension
• Regular Python files (.py) can be converted to PyGyat using the py2gyat command

Command Line Usage

Basic command structure:

$ pygyat source.gyat arg1 arg2 ...

Translation Commands

Convert Python to PyGyat:

$ py2gyat source.py

Keyword Mappings Configuration

PyGyat uses specific keyword mappings that translate Python syntax into brainrot terms. These mappings are predefined and cannot be modified:

| Python Keyword/Operator | PyGyat Translation | | --- | --- | | try/except/finally | hawk/tuah/spit on that thang | | return | its giving | | - | fanum tax | | + | rizz | | print | yap | | True | Aura | | False | Cooked | | def | bop | | while | let him cook | | import | glaze | | from | lock in | | class | skibidi | | if/elif/else | chat is this real/yo chat/only in ohio | | for | mewing | | break | just put the fries in the bag bro | | continue | edge | | assert | sus | | raise | crashout | | with | pookie | | as | ahh | | global | GOAT | | nonlocal | motion | | del | delulu | | yield | pause | | yield from | pause no diddy | | None | NPC | | pass | pluh | | self | unc | | range | huzz | | > | sigma | | < | beta | | ≥ | sigma twin | | ≤ | beta twin | | == | twin | | open | mog | | close | demure |

VS Code Extension Configuration

1. Install the extension from Visual Studio Marketplace
2. The extension automatically recognizes .gyat files
3. Syntax highlighting is enabled by default
4. No additional configuration required

Project Structure

When using PyGyat in a project, maintain the following structure:

project/
├── src/
│   └── *.gyat files
├── tests/
│   └── test files
└── README.md

Compatibility

• PyGyat works with Python 3.x
• All standard Python libraries are supported
• Regular Python keywords with defined PyGyat mappings cannot be used in their original form

Error Handling

• PyGyat will raise syntax errors for invalid keyword usage
• Python runtime errors will be displayed with PyGyat keyword mappings
• Debug information is provided in Python syntax for easier troubleshooting

Best Practices

1. Use .gyat extension for all PyGyat files
2. Keep original Python files as backup
3. Use version control to track both .py and .gyat files
4. Document any custom implementations
5. Test code in both PyGyat and Python formats