Python User Input with input()

The argument to input() is printed as the prompt, without a newline, and the cursor waits right after it. Include a trailing space or colon so the answer doesn't collide with the question:

name = input("Your name: ")
boxes = input("Lunch boxes needed (1-50): ")

A good prompt tells the user what kind of answer is expected and, where relevant, the unit or the allowed range. "Quantity?" invites answers such as a dozen or 12 boxes; "Lunch boxes needed (1-50):" makes a plain number the obvious reply. Clear prompts are the cheapest form of validation you'll ever write.

input() reads until the user presses Enter and removes the newline character from the end. It does not remove spaces, so " 12 " comes back with its spaces. Calling .strip() on the result is a common habit: answer = input("Yes or no? ").strip().lower().

input() always returns a str, even when the user types only digits. That matters as soon as you combine two answers:

first = input("Boxes for Monday: ")    # user types 3
second = input("Boxes for Tuesday: ")  # user types 4
print(first + second)                  # 34, two strings joined
print(int(first) + int(second))        # 7

+ on strings joins them, so the first print() shows 34. Convert with int() for whole numbers or float() for decimals before doing arithmetic. Check the type when you're unsure: print(type(first)) shows <class 'str'>.

Keep the raw text in its own variable when you need it for an error message, and store the converted value under a clear name, as in raw_count and count. The type casting lesson covers the conversion functions in detail.

Validating input takes two separate checks:

1. Representation: can the text be converted at all? int("three") raises ValueError.
2. Business rule: is the converted value acceptable? int("-2") succeeds, but you can't prepare minus two lunch boxes.

A while True loop with try/except handles both and keeps asking until the answer passes:

while True:
    raw = input("Lunch boxes needed (1-50): ").strip()
    try:
        count = int(raw)
    except ValueError:
        print(f"{raw!r} is not a whole number.")
        continue
    if 1 <= count <= 50:
        break
    print("Please choose between 1 and 50.")

The continue jumps back to the prompt after a conversion failure; break leaves the loop only when both checks pass. Error messages should say what was wrong and what is expected, so the user can fix it in one try.

input() reads from standard input. When a person is typing, the line simply waits. When input comes from a file or a pipe, for example python kitchen.py < answers.txt, input() reads one line per call. If no lines are left, or the user presses Ctrl+D (Ctrl+Z then Enter on Windows), it raises EOFError:

try:
    count = int(input("Lunch boxes needed: "))
except EOFError:
    print("\nNo input received; using the default of 10.")
    count = 10

Programs that will run unattended, such as scheduled jobs and automated tests, shouldn't depend on input() at all. Pass values as command-line arguments, read them from a file, or use environment variables instead. For many lines of data, read sys.stdin directly: for line in sys.stdin: loops until the input ends without raising an error.

Task: ask for a meal preference and a positive count, with a helpful response to invalid numeric text. Accept veg or meat (in any capitalisation) and a count of at least 1.

while True:
    meal = input("Meal (veg/meat): ").strip().lower()
    if meal in ("veg", "meat"):
        break
    print("Please type veg or meat.")

while True:
    raw = input("How many boxes? ").strip()
    try:
        count = int(raw)
    except ValueError:
        print(f"{raw!r} isn't a whole number.")
        continue
    if count >= 1:
        break
    print("At least one box, please.")

print(f"{count} {meal} boxes")

Test it with VEG, fish, two, 0 and 5 to see every branch. For the worked check, the type input() returns is always str, which is why both answers need processing before they are used.

The official input() documentation describes the prompt and EOFError behaviour. Continue with type casting for every conversion function, and see error handling for more on try and except. Then practise with the Python exercises and Python quiz.