kristofer

I'm struggling to see where we take the user input for the task name.

the command variable will have exit or whatever, right?

and the new <task> will actually look like new Buy Milk

so take the string and split it into a list of strings, breaking each string on the character.

If we have thought about this:

tasks = {}   # creates an empty dictionary

tasks['Buy Milk'] = 'not yet'
tasks['Start Lab'] = 'completed'

Remember start very small and build outward.

Hint 1

If you haven't already decided how to start...

This is the tasks variable.

    Tasty class.

One More List of Bad Habits

Also, be aware that some of these things are not actually related to Python but are considered to be bad practices in most of the languages (like Java).

• No comments is bad — people forget and you should comment your code. Describe why not how. Explain the intent behind the code.
• Too many comments is also bad — you should feel the border line at column 80.
• No abstractions is bad — they didn’t develop Python for you to write Assembly-style wall of code with no functions and/or classes. Copy-pasting your code is bad — use functions when you

Pythonic code refers to code that is written in a way that is idiomatic to Python, taking advantage of its features and conventions to produce clear, concise, and readable code. Here are some examples showcasing Pythonic principles:

1. List Comprehensions

Not Pythonic:

squares = []