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

updating the Debugging a Function subsection to py3k #143

Open
kylerbrown opened this Issue Jul 16, 2015 · 1 comment

Comments

Projects
None yet
3 participants
@kylerbrown
Member

kylerbrown commented Jul 16, 2015

The bug in debugging a function is no longer an issue in python 3. Should the section be removed entirely, or should a new bug be created, so students can continue to experience the joys of debugging?

One possibility would be to introduce an order of operations bug, temp - 32 * 5/9 instead of (temp - 32) * (5/9).

@rgaiacs

This comment has been minimized.

Contributor

rgaiacs commented Jul 16, 2015

The bug in debugging a function is no longer an issue in python 3. Should the section be removed entirely, or should a new bug be created, so students can continue to experience the joys of debugging?

I removed it on #142 to let the lesson consistent but I think that provide learners with some examples of debugging is important.

One possibility would be to introduce an order of operations bug, temp - 32 * 5/9 instead of (temp - 32) * (5/9).

I want a more interesting bug to solve but have no idea yet. =)

rgaiacs pushed a commit to rgaiacs/swc-python-novice-inflammation that referenced this issue May 6, 2017

rgaiacs added a commit to rgaiacs/swc-python-novice-inflammation that referenced this issue May 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment