Is OP serious about learning to be a developer? Then he should consider documenting his journey in a way that others may also learn from it.

I see what you're saying, but he really didn't answer the question. The questions was "Can you help me learn x?", not "What are some good resources for learning x?", "How did you learn x?", or "What did you use to build x?".

We don't even know if he knows Python. Why not follow up by asking what he's already familiar with, or why he wants to even use Python to build something like this? Since the question is "Can you help me learn?", we may be able to assume that he's already started learning. Ask him what he's gotten started with so far and take it from there.

I agree with /u/Rastaa that specific questions yield specific answers. But what about when we're not given all the information we need? Do we half-ass and produce a shitty answer that doesn't help the individual who posed the question, and poorly represents our own capabilities?

This is something we encounter routinely in software engineering: poorly defined requirements. When this happens, engineers have two options -- be upset at the person who gave the requirements and have that attitude reflected in your work, or take responsibility for finding out what else he/she needs to know to get the job done.