| data | ||
| .gitignore | ||
| .python-version | ||
| 01.basics-1.ipynb | ||
| 02.basics-2.ipynb | ||
| 03.identity.ipynb | ||
| 04.functions.ipynb | ||
| 05.functional-programming.ipynb | ||
| 06.generators-comprehensions.ipynb | ||
| 07.scope.ipynb | ||
| 08.decorators.ipynb | ||
| 09.modules.ipynb | ||
| 10.OOP.ipynb | ||
| 11.exceptions.ipynb | ||
| 12.inheritance.ipynb | ||
| 13.python-data-model.ipynb | ||
| 14.more-classes.ipynb | ||
| 15.linked-lists-and-arrays.ipynb | ||
| 16.trees-graphs-tries.ipynb | ||
| 17.ecosystem.ipynb | ||
| 18.testing.ipynb | ||
| 19.scientific-python.ipynb | ||
| bills.csv | ||
| file-io.ipynb | ||
| hashtables.ipynb | ||
| legislators.csv | ||
| more-decorators.ipynb | ||
| pyproject.toml | ||
| README.md | ||
| sponsorships.csv | ||
| thinking-in-list-comprehensions.ipynb | ||
| uv.lock | ||
51042 Notes Repository
How to use this Repo
I will push notes to this repository throughout the quarter. If you are keeping your own notes in this repository you should generally keep them in separate files to avoid accidental git conflicts.
Either make companion files in each directory, or keep your notes in a separate directory/notebook altogether.
I will create a notebook for each topic, numbered in the order they're introduced.
Jupyter Notebooks
There are a few ways to look at these notes:
-
You can browse these on GitHub.com in a non-interactive form.
-
If you open them in VS Code it will prompt you to install an extension for Jupyter notebooks, doing so will let you use them from VS Code.
-
If you install Jupyter locally, you have a few options for working with
.ipynbnotebooks:
uv run jupyter lab- the newer UI, will start a server anduv run jupyter notebook- the older UI, perfectly functional still- VS Code will open these in it's own editor
If you run one of the uv run options, you'll need to navigate to the .ipynb file in the window that opens in your browser.
Note: To stop a server, press Ctrl-C and then 'y' to the prompt.