Error Handling | Python for Beginners [17 of 44]

preview_player
Показать описание


#microsoftdeveloper #pythonforbeginners #learntocode
Рекомендации по теме
Комментарии
Автор

Great series; I'm learning a lot ploughing through them one by one, but:-


At 6:30 - "Let's close out our conversation about try/except...."


Except there wasn't a conversation (or introduction) to try/except. Where did it go? Did it end up on the cutting room floor, or did I nap through it somewhere in a previous video?

PuceBaboon
Автор

"If you're anything like me, and I know I am..." I knew from here, I may be in trouble focusing because of the deadpan humor. Thankfully, when you are given a line like that in this section you are presented with error handling that'll get you past it, even if you couldn't get a date in the last video.

rob
Автор

so understand the "walk away" technique...used it thousands of times and it works every time

andymouse
Автор

0:01 Causes of errors.
0:45 Error handling (impredictable - external to the applicstion) vs debugging (predictable😩).
2:40 Kinds of error: sintax errors (2:52): colon (3:40); curly braces: Java and JavaScript (4:00); runtime errors: the code is running; in principle, a problem is in the code; not in the framework or runtime; exception: the server being down: divide by zero: line (4:19); bugs are producted by code and are identified; (7:15); don't catch all errors (my note: now I understand why the Windows blue screens 😩 - 7:55); logic errors: reversed boolean: unit tests; runs but the result is not the expected one; (9:11); figuring out what went wrong: Stack Overflow, line numbers, consultation, rest (11:22).

HECTORARTUROA
Автор

Whatever happened to an explanation of Try/Catch/Finally? For a beginner, you can't just cruise thru that topic with one slide.

DrTech
Автор

11:32 In addition of explaining what the stack trace's goal, you should've explained a little bit of how the computer works, and then link that explanation to why the stack trace works like that.

avi
Автор

I know this person can talk at a normal pitch because he sometimes does, but he chooses to often not.
Quite challenging on headphones

MrSthomas
Автор

Hello,
I don't know if you add this later or if my remark is too specific but would have added a small tip on the 'if' problem : always put an "else" at the end to catch a condition you didn't expect, even if it's to test if a boolean has s true or false, 'cause python could also bring back "None" etc.

horked
Автор

I don't mind the voice pitch. Everybody can have their own personality.
For me, it is more about a sentence I heard many years ago.
"Don't let a part of what you are learning or reading left not understood, because it will keep you from focusing on what's coming".
So I have a question : Am I the only one who entered the TRY routine and run it ?
Because I should have seen the result as on the video but I got :
1_Sorry, something went wrong
3_This always runs on success or failure .
So the finally: was run too, and I don't know why.
Anybody ?

ghyslainhubert
Автор

"If you're anything like me, and I know I am"

alexshi
Автор

12:03 I can't agree any more to this. There were instances where I get stuck and then while walking outside to get dinner ideas start coming in.

NighFury
Автор

05:00 - As shown the code error is on line 4, not line 3, as the comment does count as a line. Someone edited that comment in after copy/pasting the error output, didn't they ?

AthAthanasius
Автор

Unit testing, test driven development 10:44

yogiHalim
Автор

Errors and debugging are not the same... But you said that there are 3 types of error, the first being syntax errors... should this not be classified as debugging? Since you actually said "debugging is where you know you have an issue with your code"? I'm confused.

nullspac
Автор

Saw myself speaking when you were talking about errors and crashes..sometimes they are just meant to be and we musn't freak out :) Loved the chill! :D

sunitatripathi
Автор

great video series. only gripe i have is how high his voice is, blasts my ears through my headphones when he puts emphasis on words.

Tlane
Автор

L =float(input('Amount borrowed '))
i =float(input('Interest per annum '))
n =float(input('Years to payoff '))
print(type(n))
print (n)
M = L(i(1 + i)n)/((1 + i)n-1)

Why does the last line give an 'unknown token' error with pointer at the 'n'?

vdpeer
Автор

Teaching this to my kid/niece, I can't help but wonder, why AMZN eats MSFT's lunch :-). OMG, choppy does not even begin to describe this mess.

pradeeprajurs
Автор

To avoid problems using plus (+) operator putting different variables with different types together, use comma (, ) instead.
# Example:

from datetime import datetime


today_date = datetime.now()


Days = 28


print ('February has',  int(Days),  'Today is',  str(today_date))
Result:$ February has 28 Today is 2019-09-28 07:41:47.353327

rgoliveira
Автор

HELP! #10:48 What was said there? "I would definitely look at unit testing and ...?"

shakesrear
visit shbcf.ru