Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/marioaje/Python/llms.txt

Use this file to discover all available pages before exploring further.

To follow along with Clases de Python you need three things on your machine: a working Python 3.10+ interpreter, a code editor (the course was built with Visual Studio Code, and the repository includes a .vscode/settings.json that configures the autopep8 formatter automatically), and a local clone of the course repository. The steps below walk you through each one on Windows, macOS, or Linux.

​
Installation

1

Download and install Python 3.10+

Visit python.org/downloads and grab the latest Python 3.10 or newer installer for your operating system.
  • Windows — Run the .exe installer. On the first screen, check “Add Python to PATH” before clicking Install Now.
  • macOS — Use the .pkg installer from python.org, or install via Homebrew: 
    brew install python@3.12
  • Linux (Debian/Ubuntu) — Python 3 is usually pre-installed. To install or upgrade: 
    sudo apt update && sudo apt install python3 python3-pip
2

Verify your Python installation

Open a terminal (Command Prompt or PowerShell on Windows) and confirm Python is available:
python --version
On macOS and Linux the command may be python3:
python3 --version
You should see output like Python 3.12.3. Any version 3.10 or higher is suitable for this course.
If you see command not found on Windows, Python was not added to PATH during installation. Re-run the installer and tick the “Add Python to PATH” checkbox, or add the Python directory to your system PATH manually.
3

Install Visual Studio Code

The course uses Visual Studio Code as its editor. The repository ships with a .vscode/settings.json that enables the ms-python.autopep8 formatter for all .py files, so VS Code will auto-format your code on save without any extra configuration.Download VS Code from code.visualstudio.com and install it for your platform. After opening VS Code, install the Python extension (ms-python.python) from the Extensions marketplace so you get syntax highlighting, IntelliSense, and inline linting.
4

Clone the repository

Clone the marioaje/Python repository to your local machine:
git clone https://github.com/marioaje/Python.git
Then open the cloned folder in VS Code:
cd Python
code .
The .vscode/settings.json inside the repo is picked up automatically, activating autopep8 formatting for Python files.
5

Run your first script

Verify everything is wired up by running semana1/informacion.py. This script imports the sys standard-library module and prints the major version number of your Python interpreter:
#semana1/informacion.py
#Importar una libreria de systema
import sys

#Print sirve para imprimir informacion
print(sys.version[0])

python semana1/informacion.py
Expected output:
3
sys.version is a string like "3.12.3 (main, ...)", so sys.version[0] returns the character "3" — confirming that Python 3 is active and the course scripts are ready to run.

​
Tip: Use a Virtual Environment

It is good practice to isolate project dependencies in a virtual environment. Some Week 3 and Week 4 scripts require third-party packages (camelcase, pymysql). A virtual environment keeps those installs scoped to this project.
# Create the virtual environment
python -m venv .venv

# Activate it — macOS/Linux
source .venv/bin/activate

# Activate it — Windows (PowerShell)
.venv\Scripts\Activate.ps1

# Install a package (example from Semana 3)
pip install camelcase

# Install MySQL connector (used in Semana 4)
pip install pymysql
Once activated, your terminal prompt will show (.venv) and all python / pip commands will use the isolated environment. VS Code detects .venv automatically and switches to it in the integrated terminal.

​
Repository Folder Structure

After cloning, your working directory looks like this: 
Python/
├── semana1/          # Week 1 — Variables, data types, operators, lists
│   ├── informacion.py
│   ├── variables.py
│   ├── operaciones.py
│   ├── operadoreslogicos.py
│   ├── listadedatos.py
│   └── personalizacionprint.py
├── semana2/          # Week 2 — Control flow: if/elif/else, for, foreach
│   ├── if.py
│   ├── for.py
│   ├── foreach.py
│   ├── ejercicio1.py
│   └── ejercicio2.py
├── semana3/          # Week 3 — Functions, classes, while, pip packages
│   ├── funciones.py
│   ├── clases.py
│   ├── while.py
│   ├── calculadora.py
│   └── ...
├── semana4/          # Week 4 — Dicts, file I/O, CSV, MySQL (pymysql)
│   ├── diccionario.py
│   ├── archivos/
│   │   ├── leer.py
│   │   └── ...
│   └── ...
├── semanaweb/        # Bonus — HTML fundamentals
│   ├── index.html
│   └── ...
├── .vscode/
│   └── settings.json # autopep8 formatter config
└── README.md
Each week’s folder is self-contained — you can jump directly to any week and run its scripts independently without running the others first.

Build docs developers (and LLMs) love

Get started for freeTalk to us