Closed Gchism94 closed 1 year ago
Hello, Prof. @Gchism94 . Thanks for your valuable feedback. We have addressed the given feedback and updated the proposal with the following changes:
Thank You
The Plotting Pandas!!!
Great work, your final score is the midpoint of the two: 10/10, 8/10 -> 9/10.
Dear The-Plotting-Pandas: Below is the score breakdown for your proposal. Details of things that should be updated/revised are provided in separate issues. As you address them, you should close the individual issues.
You can do this in one of two ways:
Please use the second method wherever a fix can be tied to a commit. If you preface your commit messages with "Fixes", "Fixed", "Fix", "Closed", or "Close", the issue will be closed when you push the changes to your repo. For example, suppose you want to close issue
#2
which, hypothetically, suggested that you add a new line to the README, your commit message can say something likeAdd a new line to the README, closes #2
.Once you've closed all of the other issues, close this one as well, so that going into the presentation you have no open issues remaining.
Good work! Some minor issues to fix to be eligible for full credit:
describe()
code since it will also give column types. I would also just display outputs anyway, since you don't know whether it will be significant to the viewer.