Teach the object oriented matplotlib API instead of the procedural one.#1
Open
akreuzkamp wants to merge 2 commits intonilsvu:masterfrom
Open
Teach the object oriented matplotlib API instead of the procedural one.#1akreuzkamp wants to merge 2 commits intonilsvu:masterfrom
akreuzkamp wants to merge 2 commits intonilsvu:masterfrom
Conversation
So far in course "202 - Plots mit Matplotlib" the procedural API of matplotlib was taught. This commit changes the course, to teach the object oriented API instead, which only adds additional complexity in the form of 2 lines of boilerplate code per figure, but adds a lot of flexibility. After all, the ooo API is unavoidable, even this course already used it for the multiple plots section, so it seems logical to teach it from the beginning.
After course 202 was changed to teach the object oriented API of matplotlib instead of the procedural one, this commit changes all examples in 203 and 302 to use the object oriented API as well.
Owner
|
Hallo @akreuzkamp, danke für deinen Vorschlag. Ich halte die funktionale API nicht für ganz überflüssig, man kann damit durchaus schneller etwas plotten, ohne sich Gedanken über figures und axes zu machen. Daher denke ich, dass wir schon mit
|
Author
|
Ok. Was hältst du davon, die objekt-orientierte API dann ab dem Moment zu benutzen, ab dem die Plots über einen Funktionsaufruf hinausgehen? Sprich ab dem Abschnitt "Plots gestalten", wenn es dann darum geht Axen zu beschriften, Skalen zu verändern, etc. Dass die funktionale API für sehr einfache, schnelle Plots praktischer (und dann auch "schöner") ist, kann ich nicht abstreiten. :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
So far in course "202 - Plots mit Matplotlib" the procedural API of matplotlib was taught.
For reasons I recently stated in the feedback form, I think the object oriented API is superior and should be taught from the beginning.
After all, the object oriented API is unavoidable, even this course already used it for the multiple plots section, so it seems logical to teach it from the beginning, given that it only adds 2 lines of boilerplate code per figure and nothing particularly complex for the students to learn.
This pr is a proposal, how the course could look like, teaching the object oriented matplotlib API.