How jerogutiar/python works
Project type and purpose
• This is not a full-stack application or microservice suite, but an educational code repository: a collection of standalone Python exercises (condicionales, bucles, diccionarios, funciones, etc.).
• Each directory groups exercises by date or difficulty (Básico, Intermedio, Avanzado, Moodle), and each exercise is a single Python script (often paired with a testing harness).
File structure
• Top-level “buckets” are date-named folders (e.g., 21_04_2025, 22_04_2025, 06_05_2025) and a special “Moodle” folder.
• Inside each date folder, you have either flat scripts (Ejercicio_01.py, etc.) or subfolders (e.g., 06_05_2025/1-exercises1) containing functions.py, testing.py, README.md.
• No databases, no external services, no build/deploy scripts—just source code and minimal markdown documentation.
• A global Enunciados.md provides the problem statements index.
README for additional insights
• README defines the pedagogical scope: conditional logic, loops, data structures, functions.
• Execution instructions: clone the repo, cd into a folder, run python nombre_del_archivo.py.
• Target environment: Python 3.11+, with an optional virtual environment.
a. Components
• Developer / Student (actor)
• Git remote (GitHub) – source repository
• Local file system (cloned repo) – folder tree with exercise scripts
• Python runtime (3.11+) and optional virtual environment
• Console/Terminal (I/O)
• (Optional) IDE/Text editor for code navigation & debugging
b. Relationships / Data flows
• Developer uses Git to clone/pull from GitHub → Local file system
• Developer opens IDE/Editor and navigates the folder tree → views exercise scripts & READMEs
• Developer invokes Python interpreter → loads .py script → executes logic → outputs to Console
• (If tests present) testing.py imports functions.py → outputs pass/fail results
c. Architectural patterns & design principles
• Modular organization by topic/date
• Separation of concerns: each exercise isolated in its own file (or subfolder for multi-file exercises)
• Single responsibility: each .py focuses on one problem statement
d. Key technologies
• Python 3.11 runtime
• Git (version control)
• Markdown (documentation, Enunciados.md & per-folder READMEs)
• Optional virtual environment (venv)
Elements
• Rectangles for each component: GitHub, Local FS, Python Interpreter, IDE, Console.
• GitHub → Local FS (git clone/pull)
• Developer → IDE / Console (edit/run commands)
• IDE → Local FS (open files)
• Console → Python Interpreter (run .py) → outputs back to Console
• Blue rectangles for developer tools (IDE, Console)
• Green for code artifacts (scripts, folders)
• Orange for runtime (Python interpreter, virtual env)