-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the logical ordering of Python Notesbooks #9
Comments
Thanks for the feedback! The recommended order is defined in the README which is also part of a clone. However, I agree that there would be some benefits if the notebooks would be ordered, e.g. with a number prefix in the file name. This is actually something that I've been considering in the past. I think there are certain tradeoffs. If the notebooks are not numbered, then adding a new notebook somewhere in between does not require renaming other notebooks - placing it in the preferred location in the README is enough. Also, my personal use case for teaching is to pick certain set of notebooks depending on the audience, which is painless as I don't have to rename any of the notebooks. Separate index file (similar as README but would render nicely in Jupyter Notebook) would be indeed a viable solution which would not require renaming the notebooks. I'll consider this. |
Btw, in addition to the plain README file, you can use this https://jerry-git.github.io/learn-python3/ as index. |
Added numbering also for the filenames in #35 🙂 |
When I cloned the repository on my local system, I am not able to follow the logical order of the notebooks. In other words on the Github Repository a logical order is specified against each topic as below:
But in the Cloned repository the files are in the albhatic order of the file name. There is no way to know in which order one should study. I think it will be better that we should put some index for these notebooks for easy navigation.
Also the same situation for HTML pages. There should be some logical order for those.
Thanks
The text was updated successfully, but these errors were encountered: