the improved error messages are huge I feel. Honestly they may also help pros. Like, pros will know "oh it's telling me this but really it's meaning that", but it should be less of a mental burden now when it's more like "oh it's telling me this and that's exactly what was wrong!" Really glad that parsing and typing alike are getting stronger
Those better error messages are going to be a God send to anyone trying teach/learn python. No longer will people be confused because forgetting a bracket raises an error on the following line
@@mCoding actually, in more C based languages, the error line is more accurate and the messages are more descriptive, and that's to be expected. One of the reasons I still prefere them is that. Every time I tried Python I'd get Syntax Error and then go through countless tabs trying to find why, only to realise I missed some opening or closing symbol. Even experienced people make mistakes, so having more descriptive messages will be a trully welcome addition!
3.10 is by far my favorite release since they added f-strings. Really, really great quality of life improvement with the new error messages. I'm not really a beginner anymore but they really have helped me identify small mistakes much faster.
what makes debugging to get wrong line number is that the pyc is used instead of py file some content are reorganized and comments stripped. not sure, but I guess docstrings may be sometimes removed to ensure pyc is fits into some unit of memory python uses. or may be not. who knows
Proper error messaging coming ... Can't believe, I thought sometimes it's easier to debug line by line python program to identify the issue than to get exact location and reasons from Python's error messages.
In my opinion, the greatest update in 3.10 has to be match statements. Other than that, I love the improved typing, and that types now support the '|' operator to form unions.
3 года назад+4
But I liked the "Syntax Error" where you have to figure out what the hell happened.
Is there a specific reason for waiting between pauses and not cutting the parts that you are breathing? Sometimes those parts can be annoying. If those parts are cut, I think it will be both a smooth video and more pleasant. Just a suggestion I hope you don't get it wrong
Thanks for bringing this to my attention. If I cut too close to speech throughout the vid this causes the RUclips autogenerated closed captions to fail, creating a lot more work for me. I've been experimenting with what the best tradeoff is on where to cut but if you noticed this then I clearly need to cut tighter.
@@mCoding I suspect there is quite an art to "the correct" jump cut timing. Fwiw it seemed fine to me but I also watched on double speed so the timing will look tighter for me anyways. It certainly could have been shorter. In order to closed captions problem, the thing to do is probably a cross fade? Not sure if you're doing that anyway. But effectively that should allow you to go tighter perceptually while on a per-sample-level it's smoother
Big shoutout to Pablo, absolutely awesome work.
Couldn't agree more!
Love the concise presentation format of these videos.
Thank you!
the improved error messages are huge I feel. Honestly they may also help pros.
Like, pros will know "oh it's telling me this but really it's meaning that", but it should be less of a mental burden now when it's more like "oh it's telling me this and that's exactly what was wrong!"
Really glad that parsing and typing alike are getting stronger
Pablo is a spanish core developer, check his talks in youtube, he is amazing
Those better error messages are going to be a God send to anyone trying teach/learn python. No longer will people be confused because forgetting a bracket raises an error on the following line
I always wondered why most languages can't tell you about a missing brace or similar, glad Python put in the effort!
@@mCoding actually, in more C based languages, the error line is more accurate and the messages are more descriptive, and that's to be expected.
One of the reasons I still prefere them is that. Every time I tried Python I'd get Syntax Error and then go through countless tabs trying to find why, only to realise I missed some opening or closing symbol.
Even experienced people make mistakes, so having more descriptive messages will be a trully welcome addition!
Flashbacks to C++ template error messages. Hopefully will be a lot better in C++20!
3.10 is by far my favorite release since they added f-strings. Really, really great quality of life improvement with the new error messages. I'm not really a beginner anymore but they really have helped me identify small mistakes much faster.
1:41 this was always a feature, if you read what it says it's about something different - highlighting a range instead of a single character
1:51 Wouldn't fixing the SyntaxError here then raise a TypeError? Trying to unpack int into x,y
Great vid as always. Pablo sounds like a great guy.
No doubt!
what makes debugging to get wrong line number is that the pyc is used instead of py file
some content are reorganized and comments stripped. not sure, but I guess docstrings may be sometimes removed to ensure pyc is fits into some unit of memory python uses. or may be not. who knows
This continues to be the best python channel on the internet.
Many thanks! Tell your friends!
It's getting more and more easier .. awesome 😎
Thanks ✌️
Pablo is a great person indeed
Cheers to Pablo!
I love the better error messages.
To the hero who read the documentations!
My favorite is zip's strict 🙌
No more accidentally zipping against something empty!
thank you mr james
And thank you too!
Proper error messaging coming ... Can't believe, I thought sometimes it's easier to debug line by line python program to identify the issue than to get exact location and reasons from Python's error messages.
Love the high level vids
In my opinion, the greatest update in 3.10 has to be match statements. Other than that, I love the improved typing, and that types now support the '|' operator to form unions.
But I liked the "Syntax Error" where you have to figure out what the hell happened.
That's how you can tell you're a true veteran
Very cool! :) Btw, what mic are you using now?
I'm using the AT2020 XLR
@@mCoding Thanks!!
every time i forgot to close a brace, i just assume that the error was near lol
Thanks.
Welcome!
Niiiice
I thought they were going to name this one 4.0
I'll make a video on this probably...
@@mCoding I don't think a whole video is necessary to explain the python versioning, you could probably fit that all in a 'short'
FIRST: like your vides
...y is it still writen "0 Comments" :0 Am i deaaaaaaaad.
*x-files sounds*
thanks pablo o7
Help me
My current knowledge is out of date after only 3 to 4 years. I think it might be time to re-learn the language.
I couldn't even upgrade to 3.9 without bugs and people are talking about 3.10 😶
Production code is probably still stuck on 3.7 :)
@@mCoding More or less 2.7 ;)
up
HELP
Is there a specific reason for waiting between pauses and not cutting the parts that you are breathing? Sometimes those parts can be annoying. If those parts are cut, I think it will be both a smooth video and more pleasant. Just a suggestion I hope you don't get it wrong
Thanks for bringing this to my attention. If I cut too close to speech throughout the vid this causes the RUclips autogenerated closed captions to fail, creating a lot more work for me. I've been experimenting with what the best tradeoff is on where to cut but if you noticed this then I clearly need to cut tighter.
@@mCoding I suspect there is quite an art to "the correct" jump cut timing.
Fwiw it seemed fine to me but I also watched on double speed so the timing will look tighter for me anyways. It certainly could have been shorter.
In order to closed captions problem, the thing to do is probably a cross fade? Not sure if you're doing that anyway. But effectively that should allow you to go tighter perceptually while on a per-sample-level it's smoother
I find your timing very good. Gives me some time to ponder about what you said. Please keep it this way.
3.10 ? Okay no, so it means that we'll go from 39 to 310 ? that will break the sorting of the installation paths of python versions, meh