How yendro/python-learning works
Project type and purpose
• This is not a multi-tier web app or microservice suite, but a single‐user Python notebook repository for documenting exercises in a “Python Programming” MOOC.
• The goal is to show how your local environment, Jupyter server, Python kernel, notebooks and version control interact.
File structure
• Top-level files:
• .gitignore, LICENSE, README.md – typical Git repo control/config files
• notebooks/ – directory containing sequentially numbered Jupyter notebooks
• There are no separate “frontend” or “backend” code directories, tests, or deployment scripts.
README for additional insights
• Specifies a sequence of notebook topics (basics, conditionals, loops, … data structures)
• Emphasis on a local, iterative learning workflow.
Main components
a. User (you/the student)
b. Jupyter Notebook Server (process that serves notebooks over HTTP)
c. Python Kernel (actual execution engine behind each notebook)
d. Local File System (where notebooks and config files live)
e. Git CLI (version control interface) & Remote Git Host (e.g., GitHub)
f. Python Environment (virtualenv/conda with installed packages)
Relationships & data flow
• User ↔ Browser ↔ Jupyter Notebook Server
• Notebook Server ↔ Python Kernel (execute & return outputs)
• Kernel ↔ File System (read/write .ipynb files in notebooks/)
• User ↔ Git CLI → commits/pushes to Remote Git Host
• Python Environment underpins both the Notebook Server and Kernel
Architectural patterns or design principles
• Single‐page app pattern: Notebook UI served by server, communicates with kernel over WebSockets
• Version control usage for incremental progress & backup
• Separation of concerns:
• Presentation/UI (browser + notebooks)
• Execution (kernel)
• Storage (file system & Git)
Relevant technologies & frameworks
• Jupyter Notebook (frontend + server + kernel)
• Python 3.x environment (virtualenv or conda)
• Git for VCS, GitHub (or equivalent) as remote host
• Browser (Chrome/Firefox)
Essential elements
• Clear labels: User, Browser, Notebook Server, Python Kernel, File System (notebooks/), Git CLI, Remote Git Host
• Browser → Server (open notebook, run cell)
• Server → Kernel → Server (execute code, return output)
• Server → File System (save .ipynb)
• Git CLI → File System (commit) → Git Host (push)
• Yellow for user interface (Browser)