Public lecture materials for Software Programming (IGS1931), Inha University.
This repo holds Thursday lecture notebooks and take-home homework
assignments — no solution keys. One folder per week for lectures, e.g.
week02-functions/, plus a top-level homework/ folder for homework
notebooks. Each lecture notebook is meant to be opened and run in Google
Colab during its own class, then continued locally afterward.
| Week | Topic | Notebook |
|---|---|---|
| Week 2 | Functions — From Repetition to Reuse | |
| Week 3 | Functions Practice — Building Fluency | |
| Week 5 | Conditionals and Recursion — Practice |
| Week | Topic | Notebook |
|---|---|---|
| Week 3 | Functions Homework | |
| Week 5 | Conditionals and Recursion Homework | |
| Week 5 | Rock Paper Scissors Assignment (submit Levels 1–4+) | Instructions · Starter .py |
Pick whichever fits your machine.
Running code in Colab requires signing into a Google account. On a shared lab PC, don't sign into your personal or student account in the regular browser window — use an incognito/private window instead, so nothing stays logged in for the next person:
- Open a new Incognito/Private window (Ctrl+Shift+N / Cmd+Shift+N).
- Sign in with your student email — just for this session.
- Click the Colab badge above for the notebook you need.
- Immediately do File → Save a copy in Drive. That creates your own private, editable copy — editing the shared link directly will conflict with everyone else opening the same one.
- When you're done, sign out of the Google account and close the incognito window.
git clone https://github.com/abdukarimovhm/software-programming-lectures.gitOn GitHub, open the week's folder → open the .ipynb file → click the
Download raw file button (the down-arrow icon above the file), or
right-click the "Raw" link and choose "Save Link As…".
Once you have the file (Option B or C), skip to Running Locally below.
Once you're past the first Colab session for a topic, work locally instead:
- Get the files — see Getting a Working Copy above (Option B or C).
- Create a virtual environment (once per machine, from the repo
folder):
python -m venv venv
- Activate it — every time you come back to work:
- macOS/Linux:
source venv/bin/activate - Windows (PowerShell):
venv\Scripts\Activate.ps1 - Windows (cmd.exe):
venv\Scripts\activate.bat
- macOS/Linux:
- Install dependencies:
pip install -r requirements.txt
- Open the notebook:
- VS Code: install the Python and Jupyter extensions, open the
repo folder, open the
.ipynbfile, and pick yourvenvas the kernel (top-right of the notebook toolbar) before running any cell. - PyCharm (Professional): open the repo folder as a project, open
the
.ipynbfile, and set thevenvyou created as the project's Python interpreter (Settings → Project → Python Interpreter) before running cells. (PyCharm Community doesn't support.ipynbfiles directly — use VS Code or plain Jupyter instead.) - Plain Jupyter (any editor): with the venv activated, run
jupyter notebookand open the file from the browser tab it opens.
- VS Code: install the Python and Jupyter extensions, open the
repo folder, open the
You only need to repeat steps 2-3 (create/activate) once per machine —
after that, just activate the existing venv each session.