Print to console

Console output

1 Brave new world

Variables introduction

Data Types in Python

2 A warm welcome

String interpolation

Python naming convention

3  The resistance base

Comments in Python

Python problems practice

4 The mission

If statement

Bool type introduction

5  Back to the streets

Reading From Console in Python

Nested conditionals

6 Who is your friend?

Introduction to for loop

Introduction to a float type

7 The basement

Introduction to while loop

Introduction to functions

8 Reparing Noname

Introduction to lists

Lists - advanced operations

9  Victory is close

Modules

Modulus operation

Python test

10  Wonderland

I was about to make coffee when Tom entered the kitchen. 
"Hi Teo, how are you?" he said, leaning against the counter. 

I had seen that body language before and was pretty sure this wasn't small talk. "Is this a 'what is happening in your life?' kind of how are you, or the 'just answer fine' how are you?" I asked. 
"You're getting to know me," he said, "This is the 'what's going on in your life' one. I don't ask questions just for the sake of asking." 

"Well," I began, "In the last few weeks, I was dragged forward through time by a former acquaintance, I'm fighting in a war that I don't fully understand, and I don't know if I'll ever see my family again, and..." I paused for a breath before I got to the worst. I wanted my last point to come through loud and clear. "Do you know what pisses me off most of all?"

"Milk, Tom! You have no Goddamn milk in the future! How am I supposed to drink coffee? Without milk? What is wrong with this world? I don't understand..."

"Sorry to hear all that, Teo," Tom interrupted. "Any chance we can rewind this conversation and change that 'how are you' to the 'just answer fine' one?" 
"That's what I'm talking about!" I continued. "No one cares about my feelings here. Everything is predefined; I do not influence what's going to happen. The same as programs that I write..." Now that I had aired my grievances, my mind began to settle down and float back to coding.

Wait a second, I thought. Predefined... as a matter of fact, my programs are predefined, and that's what's wrong with them. When I get up in the morning, I don't know the air temperature outside. Then I check it, and if the temperature is low, I wear a heavy jacket; otherwise, a lighter coat. But in the program I wrote, the temperature is predefined and ALWAYS -10 degrees. It works the same way in winter, summer, or spring. Why would you write a program that tells you what to wear if it always says the same thing?

"Tom," I asked, hoping he wasn't too put off at this point, "I need a way to provide some outside information to my program. I want to check the real temperature and have my program decide what I should wear based on that. Can you help me?"" 
"You are asking difficult questions, Teo. If it will make you feel more comfortable here, then yes, I know one command that will help. But let's keep it a secret from Ritchie, ok?" 
I wasn't sure why this had to be kept from the leader, but I desperately wanted to learn more about coding. "Sure!" I said.

Tom was clearly more comfortable with computer code than conversation. "There are many ways to provide info to your program, Teo. You can read info from a file stored on your computer or from any device connected to your computer or you can connect to the Internet and read info from there. You can also 

"The same console that I'm writing to when I use a print(...) command?" 

"Yes, Teo. Exactly. I only know about console input; for the more complicated methods involving files and the Internet, you'll have to ask someone else. However, those methods will be easier to understand if you learn the simpler console input first."

The console is a text area that we treat as a sequence of strings

(or lines). When using the print(...) command, you add one new line to the console. 

To read a line from the console, you use the

 command read? For example, what if I have written two lines to the console?" 
"Oh, you are funny, Teo. It doesn't work like that. There is no point in reading from the console what you have just written there from your code. You already know what it says! 

When you use the input() command, the program execution stops and waits for the user to input data to the console - to type some text! 

When the user finishes their input and presses Enter, 

input() returns a string containing that data.

"This is a basic program with both input() and print() commands. 

First, you tell the user what you want them to input. Then you read it in and do something with that data.

"Does it make more sense now?" Tom asked. 
"Aha, I see now," I said.

By the way, you can place the text that asks the user to input something directly in the 'input' command, this way your code looks neater. The only caveat is that you need to add '

' at the end of the text, as Python doesn't automatically go to a new line after the input.

' is a symbol that is secretly added to the end of each line, that instructs to go to the next line. 

 automatically adds it, and you don't need to think about it, but 

"Both versions are correct, one just has less code than another," Tom added and continued, "In the terminal where you solve tasks, there is an area called the Console input. We will use that to provide input to your program. When your code runs an input() command, it will read one line from the Console Input window. Try it!

"Thanks, Tom, those examples really brought it together!" I said, grateful that he hadn't left after my earlier ranting. "Now I can build programs that take in data from the outside. Is there anything else neat about the Console input you can show me?" 

. This means you can't apply arithmetic operations on input, because Python doesn't know if it is a number you want. For example, this is wrong:"

Tom continued: "And to make it right, you need to 

, which will explain to Python to treat the input data as an integer

"Be aware that if the user of your program inputs a string instead of a number, your program will exit with an error (crash)!" Tom tried to sound dramatic, to emphasize the disaster of a crashing program, "You will learn later what to do, to keep your program from crashing, and now here are some exercises for you to sharpen those new skills:"

To speed up world salvation, in all future tasks, we are going to omit the part where you explicitly ask a user to input a value unless otherwise specified (for example, "Input a number" or "What is your name"). Your program should read an input value immediately, without first printing a prompt.

"Now Teo, with such a powerful tool in your hands, you should practice A LOT. Info about 

 is a top-secret here in the base. I'll share some practice tasks with you, but don't tell anyone about our lesson today. Good luck!" 

Tom sent me a file with tasks. Later that day, I closed the door to my room, sat on the floor with my laptop, and opened the file. Here is what I found inside:

 
The person who solves all the tasks from this document can open the door to the underground storage of the resistance base. For root users only. 
To be sure that you are the leader of the resistance base, we protected the key to the underground storage. You will be given 6 tasks; if you solve them, the secret key to the storage room will be revealed. These tasks contain advanced operations of the Python language that only base leaders have access to. FOR YOUR EYES ONLY. Never tell anyone what you have seen in storage. Good luck!

As soon as I finished the last task, the promised message appeared on my screen with the secret code: 

Discover how to capture user input in Python with our easy-to-follow lesson. Start reading from the console and enhance your Python coding skills at CodeEasy.io.

Company

Learn More

Extras

Contact