# A 32-notebook Python course kept as Jupyter files in one repository > The AccumulateMore/Python repository is a completed Chinese-language Python course stored as numbered Jupyter notebooks, from the print function through files and packages, with a companion data folder that has to sit next to the notebook files. It is a learning resource with a marketing wrapper, and it carries no licence. **AccumulateMore/Python** — ✅（已完结）超级全面的 Python 笔记【马士兵教育】 - Repository: https://github.com/AccumulateMore/Python - Stars: 646 · Forks: 135 - Language: Jupyter Notebook - License: not declared - Published: 2026-10-21 · Updated: 2026-10-21 · Language: en - Canonical page: https://hysenlabs.com/projects/accumulatemore-python ## One ordered course, numbered notebook by notebook The repository is a Python course delivered as Jupyter notebooks, and the organisation is what makes it useful. Every file is prefixed with a two digit number that fixes the teaching order, starting at the print function and running to file I/O, with a separate directory for the editor setup that comes first. The sequence in the file listing follows the way a language is actually taught rather than the way a reference manual is arranged. It starts with output, then escape characters and raw strings, then binary and character encoding, then identifiers and reserved words, then variables, assignment and the common data types. It moves through type conversion, comments, the input function and the operators, then into program structure with the sequential form, the truthiness of objects, branching, the conditional expression and the pass statement, and the loop family with range, while, for-in, nested loops and break with continue. The second half covers the data structures, lists, dictionaries, mutable and immutable sequences with tuples, sets and strings, and ends with functions, exceptions and debugging, classes with shallow and deep copies, modules and packages, and file reading and writing. There is also a related_data folder at the root that holds the assets the notebooks expect. ## The related_data folder has to travel with the notebooks The most concrete piece of setup advice in the project is a one line instruction that saves a lot of confusion. The files in the related_data folder need to be placed in the same directory as the ipynb code files, and only the empty related_data folder itself should be kept in the repository. That last part is a version control convention rather than a functional requirement, and it makes sense: the notes are meant to be run and the data files are meant to be copied next to them on the reader's machine. The reason this is worth calling out is that the repository is a set of notebooks rather than a package, so there is no installation step that could arrange the layout for you. Nothing is on PyPI, there is no setup.py and no test suite to run. You clone the repository, open a notebook, and the working directory has to look right. The topics tagged on the repository include python-resources, python-libraries and python-framework, which signals the intent that this is a learning collection rather than a single importable library, and the primary language is recorded as Jupyter Notebook rather than Python for the same reason. ## Open the notes with Anaconda's Jupyter, not an editor plugin There is a rendering caveat that the project spells out, and it has a concrete consequence for how you set up your environment. When the notes are viewed online, images and formulas sometimes display incompletely because the hosting site has not parsed them properly, and downloading the notes and viewing them locally fixes it. The project does not offer a download recipe, it suggests looking up how to download files from GitHub, or it points at the editor directory in the repository. The second caveat is about the editor. Opening a notebook with PyCharm's Jupyter Notebook support does not display the images correctly, and the notes are meant to be opened with Anaconda's Jupyter Notebook instead, with the editor directory containing the instructions for that. The third note is about navigation, because a course with 32 files needs a table of contents, and the project recommends installing the directory extension for Jupyter Notebook so you can jump to a chapter quickly. So there is a small setup tax before the content is usable, and it is a tax worth paying once rather than discovering piecemeal. ## The course is tied to a video series from one instructor These notes are the written companion to a video course, and the documentation points at a single bilibili video by the instructor's team, with the training school named as the speaker. That relationship shapes what the notes are. A notebook is the right format for a course built around running code, because each cell is executed and read in sequence, and a transcript beside it carries the narration that a static tutorial page cannot. It also means the notes are not a language reference. They reflect one person's pedagogical ordering and one course's pacing, and the topics on the repository, including awesome, collections and python-resources, describe a curated shelf of content rather than a coherent library. There is no version compatibility statement either. The content covers the sort of fundamentals that have not changed, which is a point in its favour, but nothing in the repository tells you which Python version it was written against, and a note that teaches one approach to, say, exception handling is not going to discuss the alternatives that exist today. ## The rest of the repository is a course advertisement Roughly two thirds of the readme is not about Python at all. It is a recruitment funnel for study groups, resume coaching, paper guidance, internship and job placement help, and referral lists for a long list of employers. The groups are WeChat based, with a note that the QR code entry method has stopped working and that people have to be invited by the author, and a row of request examples that mix community access with paid services. There are referral tables listing dozens of companies, internship and job placement claims, and screenshots of what it calls an annual referral ranking, with the same sentence about not taking detours repeated several times in a row. This is worth naming plainly because it affects how you evaluate the project. The technical content is genuine and free, and the marketing is not hidden, but the repository is also a storefront for paid coaching, and the same person is the author of the notebooks and the seller of the service. That is not a reason to avoid the notes. It is a reason to read them for what they are, a well organised free course, and to be clear-eyed that no code review, issue triage or bug fixing will come back to you through the repository's issue tracker. ## What you get and what you do not The value proposition in one paragraph: a beginner or someone returning to Python after a break gets a single ordered path through the language with runnable examples, in Chinese, with the common beginner stumbling blocks handled explicitly. The escape characters and raw strings get their own notebook, as do binary versus character encoding and identifiers versus reserved words, which are exactly the topics that separate people who can write Python from people who can only copy it. Objects and their truthiness, the difference between mutable and immutable sequences, and shallow versus deep copies each get dedicated attention too. What you do not get is a maintained project. The repository records no licence, which means the terms under which you may reuse the text or the code are not stated, and for a teaching resource that is a real limitation for anyone planning to build on it. There are no GitHub releases, so there is no version to pin, and the last push was on 2026-09-20, with the description marking the course as completed. For a resource that is finished rather than finished and growing, that is arguably the right shape, and the one thing to confirm before you rely on it is that the licence question does not affect how you intend to use it. ## Conclusion Adopt this repository as a structured reading path if you are a Chinese-speaking beginner who wants one ordered course rather than scattered tutorials, and you can follow the Jupyter workflow it assumes. Skip it if you need a maintained library, a testable codebase or something you can build on, because the repository records no licence, publishes no releases and its last push was on 2026-09-20. Before you start, set up Anaconda's Jupyter Notebook rather than an editor plugin, because the notes assume that renderer, and copy the related_data folder next to each notebook file or the examples will not find their assets. ## FAQ ### What is in the AccumulateMore/Python repository? It is a completed Python course stored as 32 numbered Jupyter notebooks, running from the print function and data types through control flow, data structures, functions, exceptions, classes, modules and packages, to file reading and writing, plus an editor setup directory and a related_data folder for the assets the examples use. ### How do I open the notebooks so the images and formulas show correctly? The documentation recommends Anaconda's Jupyter Notebook rather than an editor plugin such as PyCharm's Jupyter support, which does not display the images correctly. It also recommends installing the Jupyter Notebook directory extension so you can jump to a chapter, and notes that viewing the notes locally works around incomplete rendering on the hosting site. ### Why do the notebooks need a related_data folder next to them? The files in related_data are meant to be copied into the same directory as the ipynb code files, with only the empty related_data folder kept in the repository. Since there is no installation step that arranges this, the layout has to be set up by hand after cloning. ### Is the AccumulateMore/Python course actively maintained? The description marks the project as completed, the repository has no GitHub releases, and the last push was on 2026-09-20. The repository also records no licence, so the terms for reusing the notes or the code are not stated there. ## Sources - [AccumulateMore/Python on GitHub](https://github.com/AccumulateMore/Python) - [Issues](https://github.com/AccumulateMore/Python/issues) - [README](https://github.com/AccumulateMore/Python/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/accumulatemore-python