Print Out, Input In

A program can show you things and ask you things. print("Hello") puts Hello on the screen. input() stops and waits until you type a line and press Enter, then gives your line to the program. Here is the catch worth remembering: input() always hands back text, never a number. If you type 12, the program receives the characters 12, which is a str — not the value 12. Adding 1 to it would fail. To get a number, the program wraps the text: int(input()) reads the line and turns it into a whole number you can compute with.

print(...) writes its arguments to the screen, then moves to a new line. input(prompt) shows the prompt, pauses the program, and returns everything you type up to Enter — as a str, always. This is the classic first-week surprise: age = input() followed by age + 1 raises an error, because age holds the string "17", not the number 17. The fix is a conversion: int(...) for whole numbers, float(...) for decimals. So age = int(input()) reads the line and converts it in one step. Output goes out as text; input comes back as text; numbers you have to ask for on purpose.

print and input are your program's two channels to a person: print writes a line to standard output; input reads a line from standard input and returns it with the trailing newline stripped. The return type is invariably str. This is deliberate — the program cannot know whether the characters you typed were meant as a number, a name, or a command, so it hands back the raw text and lets you decide. Converting is an explicit act: int("17") gives 17, but int("cat") raises a ValueError, which is Python honestly reporting that the text was not a number. Read the input, convert it, and check it — three separate responsibilities you will meet again and again.

Two words let a program talk with you. print shows words on the screen. input waits for you to type a line and press Enter. Print sends out. Input takes in.

Whatever you type, input hands back as text. Even if you type 7, the program gets the word 7, not the number. To do math with it, the program must turn the text into a number first.

input() is a thin wrapper over reading a line from the standard input stream; it blocks until a newline arrives and returns the line minus that newline, typed as str. There is no type inference at the I/O boundary — the edge between a program and the outside world is untyped text, and turning that text into structured values (parsing) is the program's job, not the runtime's. This is why robust input handling pairs conversion with error handling: int(s) is a partial function from strings to ints, undefined on "3.5" or the empty string, and a program that trusts its input without guarding the conversion is one malformed line away from a traceback. The habit of never trusting the shape of external input begins here.

The str-typed boundary of input() is an instance of a general principle: the edge of a system is untyped, and parsing is the act of lifting unstructured input into a typed domain where invariants can be enforced. int : str ⇀ int is partial, and a mature program makes the partiality explicit — validating, or catching ValueError — rather than letting an unhandled exception define its behaviour on bad data. Output is the dual: print serialises typed values back down to text via str(...), an often lossy projection. A surprising amount of practical software lives at exactly this membrane, converting between the disciplined interior of typed values and the formless text that people, files, and networks actually exchange.