Python Debugging (PyCharm + VS Code)

[@xelaxander]

What separates mcoding from the rest of the Python KZbinr crowd is the fact that even before watching the video, I know my time won’t be wasted. Love your work, hope you consulting company is doing well.

[@_jaime.]

Totally agree, I feel like he's the only Python youtuber who's able to teach me something new on every single video

[@jeroenvermunt3372]

I am just replying to reinstate your comment, I couldn't agree more. He also is the only one who dives deep into 'boring' subjects, but which are essential for developers. For example this video, but also logging, packaging and testing.

[@DominicCarrier]

As an entirely self-taught software developer, I can attest that these kind of introductory videos are always great. It never assumes "well known knowledge". #mcoding is a very nice resource for all skill levels. Love the channel.

[@LastTigerEyes]

I am always impressed how I still learn things from your videos, even on topics I'm familiar with already (TIL about conditional breakpoints).

[@olo90]

Finally a video on debugging for Python. Haven't even watched it yet but I've got big hopes that this will be the video I'll send to every new intern & junior in our team at work 😀

[@adamfarquhar1279]

I've found setting up the debugging in VS Code to be surprising. Now I know it's not just me! Thanks for the clear explanations and work-arounds for the quirks in the PyCharm and VS Code debugger settings.

[@josephpierce8926]

Wanted to say thanks. I didn't know any of this, and it seems super useful. Bonus tip for anyone who has to run their code from the command line, you can add the call breakpoint() in your source file and then use the debugger from the terminal

[@powrusr]

Since you recommend testing, I'd love to see more content on testing the hard stuff like API's, files, databases with pytest. Testing static code is easy the IO stuff is more complicated. Thanks for the nuggets! 💪

[@DanielLavedoniodeLima_DLL]

Using the debugger is something that I've procrastinated learning since I began programming in university 10 years ago. Nice to see such a comprehensive video about that topic #mcoding

[@goost0852]

More basic than the usual, but still a nice refresher :)

[@drBnpD]

Whoa! Another gem from #mcoding! 🌟 Clear, conceptual, and oh-so-needed. Keep 'em coming! 🚀

[@user-bp6eh7en1v]

13:47 really nice to see him laugh at something goofy like this 😄 #mcoding

[@Schlynn]

Really been enjoying your videos alot more recently as I've been diving deeping into Python. Thank you for the upload.

[@sebsafari]

Wow super helpful video! I've used the debugger for a while but seeing your methodology to it was insightful. I would have changed the data in the file rather than the function, but you don't always have that luxury.

[@jeffglass5196]

Genuinely, I applied some new things I learned from this video within half an hour. Thank you for all you do. #mcoding

[@AFurreh]

Genuinely had no idea about conditional breakpoints. Big time saver! #mcoding thank you much for going in to this topic!

[@loic1665]

Great video ! Love the last advice about unit testing! I've personally had to debug asyncio app and it's really hard!

[@justingerber9531]

Awesome video as usual! I never knew about conditional break points, seems super useful, I’ll have to try them out! Also I’ve been learning and implementing testing lately. It’s hard to write good tests, but once tests are written it is such a joy to refactor and improve code knowing you have your tests as a sort of safety net. Thanks for the video #mcoding!

[@mojo9Y7OsXKT]

As far as a beginner live debug tutorial is concerned #mcoding has done an excellent job in this vid. I am a seasoned quant programmer and tend to often develop code in live debugging mode. With interpreted languages like python and matlab this is not as important, but with something like C/C++ its very handy.

[@ilyagrant]

Again and again you manage to talk about things that I dealt with but never knew how they should be applied. Thanks for your content! #mcoding

[@SyberiaK]

As a professional print debugger user, I'm absolutely amazed that these live debuggers exist :D You did a great job explaining them #mcoding

[@levatius4397]

I am always surprised how many people don’t know about live debugging, also big PyCharm fan 🎉 #mcoding

[@Phaust94]

#mcoding Man, 6 years into Python development and never knew about conditional breakpoints in PyCharm. Sweet!

[@danielschmider5069]

good video, you'd be surprised how many people never learned to properly debug and just use print debugging. Nothing against print debugging if it gets the job done, but in my experience it takes more trial and error because you have to know what to print first - while debugging gives you the chance to inspect all variables during runtime and see them go through different states and values. You end up finding the problem so much quicker, and never have to delete your print statements after you're done debugging. thank you #mcoding

[@FrancisCharetteMigneault]

Thanks for the info about PyCharm's setting for Python 3.12 debugging. That will be useful in a near future for sure! #mcoding

[@RoysIdea]

Alas I can’t place a comment in the main thread, so hope someone or #mcoding is able to answer how to debug when starting from the command line with arguments. Otherwise I’m forced to use the print statements

[@replicaacliper]

Super useful to people who aren't from a cs background, as a physicist i use Python all the time but I've never learned how to debug, I just place print statements everywhere haha

[@stevengorlich4993]

#mcoding after 10 years with python, I still learn new stuff with your videos. I pushed my C-board to give us professional pycharm licences, wished I had a personal one as well :)

[@TheMathman7]

Breaking on uncaught exceptions is very handy as well!

[@failgun]

This is the main problem I had with my university's Python course, we did 12 weeks of it, and they introduced lots of concepts - variables, strings, types, functions, classes, etc. It wasn't bad for an intro-to-programming course taught with Python. But they didn't mention how to use our IDE's debugging tools _once_ . I found out about it later and I was baffled that they willingly let us believe there was no better alternative than littering our code with print statements (this was even encouraged) to figure out what was going on.

[@adrianfletcher8963]

I finally ripped the bandaid and used the debugger for the first time 😅. I was like wow all these print statements are so useless. I'm glad mCoding is scratching the itch further. He said to debug in his python nooby video, but it still doesn't mean that we got that full tutorial #mcoding

[@Ignisami]

Print statement debugging is never *entirely* useless. Code can behave differently when you're in the debugger. To give but one reason: Each step of the code takes longer (because you're reading what the debugger says, for one), things have all the time in the world to resolve before moving on. When you actually run the code normally that may not always be the case.

[@adrianfletcher8963]

@@Ignisami That's true. I think I'm still getting used to the capability and am having "everything is a nail" syndrome at the moment t

[@mattjax16]

Jetbrains debugger is why I fell in love with jetbrains products in the first place vs code can’t compare lol

[@mattjax16]

Well I’m sure it can but I don’t feel like learning until now lol

[@aliwelchoo]

Conditional breakpoints is a big new one for me. Will be using that! Only thing I don't understand is why your pycharm debugger doesn't drop straight into a breakpoint upon exception?

[@Mayur7Garg]

Conditional breakpoints in VSCode also allows for hit counts and triggered breakpoints instead of expressions. Hit count based breakpoints are good for loops and triggered breakpoints are good when you want to break only when a previous breakpoint was hit. #mcoding

[@pipurs]

I can safely say that the debugger, any debugger as a matter of fact, has been my best tutor. Not only regarding my own code, or my college's code, but also down there in the nitty gritty of things. But then I'm a 100% autodidact - which means that I've stared at some amount of exceptions through my years... Debuggers ftw.

[@NicolasJoye]

Thanks, Jetbrains, for providing the licenses!!!

[@kitschlab]

Thank you #mcoding for this! I can't believe I never used the python debugger. Can't wait to try it out.

[@NikitaSerditov]

#mcoding is a truely useful Python programming channel. Thanks a lot.

[@MattiasBrunschen]

Just started to use vscode, so your hints are very helpful. Thank you, #mcoding .

[@timothyhumphreys1231]

As a professional print debugger myself I found this video super helpful! #mcoding

[@jasperkousen5470]

Thanks for all the great content!

[@Th3Vitamine]

Next logical step to cover would be remote debugging, and maybe some cli variants, like pudb. Also a neat feature is python cells in VSCode (denoted by #%%) #mcoding

[@cristianbitica8204]

I'm surprised of how much I can learn from these videos. #mcoding

[@BartDorlandt]

Thank you for yet another great video. Quite nice you showed both vscode and pycharm! #mcoding

[@nHans]

So you're saying that as far as the contest is concerned, the winners are determined by random draw, so the quality and relevance of my comment doesn't matter? All I need to do is type #mcoding somewhere in my comment? Awesome!

[@robotnaoborot]

you can put import pdb;pdb.set_trace() in your code to debug it without using editor. I think it's at least worth mentioning

[@castercs]

em stupid question .. do you have some python course? Udemy or similar

[@АртемФедоров-ю7б]

It worth mentioning that before debugging, engineer must read log message first, maybe he can get some clue there

[@gregkeith9521]

Reminds me of VBA debugging. Very good explanation #mcoding

[@moejo8187]

I didn't know the conditional breakpoints. Thanks for the explanation. #mcoding

[@hargrav3s740]

Love a nice debugging session breakdown, when I joined the industry, live debuggers truly are king! (That and good logs) #mcoding

[@shabik3]

Noice, this is a holy grail of python vids!! :D

[@richwiss]

Hey! Thanks for the videos (as always). Been a long time vscode user but would be super happy to try pycharm! #mcoding

[@fluffykitties9020]

very interesting, printing can become unbearable. this is also a great way to learn coding. i'm a vscode user but wouldn't mind trying pycharm.

[@tnemgarf89]

Throughout this tutorial I thought to myself, at least five times - "Oh, how exciting video this is!" What a nerd I am.....

[@jeevan1016]

What is the efficient way to debug a function that is used in threading? Please give us some insights on this topic.

[@tooru]

Of course I want a license too #mcoding but still thank you for producing such useful and polished content. We can see that you care about making it better.

[@kall2075]

#mcoding need more videos like this. Preferably on more complex code base where the issue is on the import code

[@NimeshVellera]

#mcoding is one of the best KZbinrs in the python space. His videos are simply amazing.

[@kayebennett7867]

#mCoding, usually I enjoy your videos because you really go deep into the details, but I felt that you only touched the surface on this one. I don't use pycharm or vscode but I imagine that you can also use pdb commands, I think these are really useful for proper debugging. For example, in 15:12, you could have just used the "until" command to exit a loop instead of setting a breakpoint that you have to remove immediately after.

[@moonskined]

I recently started learning python so this was very helpful. Thank you. #mcoding

[@archiemarqx]

I use python for Data Science, so in this case I use both, VS Code for coding in Jupyter Notebbok and PyCharm for Python, and this combination works like a charm to me #mcoding

[@Acuzzio]

What an excellent video. Thanks a lot.

[@nikitkuzi]

What are the best beginner projects to fill your portfolio and to gain experience that you can recommend? #mcoding

[@potzko2552]

tbh I find that the breakpoint() function is a bit of the best from both worlds of a live debugger and print debugging I usually put it behind an if :) #mcoding

[@dataplatter]

What about testing code that might not get run in normal circumstances? Also, is there a way to step back in program state? #mcoding

[@thegothaur]

Nice video. I noticed that, for some reason I don't understand, Pycharm debugger doesn't work if code is async and I have to use pdb :(

[@marekmdpdesign]

Nice, learned few new things when it comes to debugging :) - btw what does mean in your test code for e.g.: „actual = load_recipes(…)” - the three dots as arguments? #mcoding

[@vytah]

... is the ellipsis literal. It's an object of type EllipsisType, similar to how 1 is an object of type int

[@Jakub1989YTb]

pycharm has the best debugger in the business!! #mcoding

[@jesusromero9167]

This is gold! It would be amazing if you make a series of how to use pycharm the way is intended #mcoding

[@Landee]

Need more beginner tips !! #mcoding

[@fairphoneuser9009]

Print debugging is sadly so popular that people don't even care about real debugging and don't know its capabilities. But this doesn't mean that I'm not using print debugging for some specific purposes. #mcoding

[@redbeangreenbean]

This was immensely helpful. Thanks #mcoding!

[@lakshman587]

In vscode when debugging, if we save something then every time we have to restart the debug session, is there any way to automatically restart the debug session after we save the file?

[@harshmodi5627]

Knowing how to debug makes life so much easier #mCoding

[@maciejbrzeski9740]

Wonderul video as always. I learn a lot new things every time. Thanks for all your effort that you put in those videos! #mcoding

[@mytelevisionisdead]

Pycharm is where it's at!!! ❤❤ 🙏 #mcoding

[@jayp2570]

Yes I love pycharm too!

[@Excgo]

@mCoding The code you have given in the git repo is the already fixed version. Is that by decision or should the buggy version be in the repo?

[@everorlandoreyesruiz9789]

Awesome vid, thanks 👍

[@Articha]

Sometimes info from videos shock me. Keep going, James! #mCoding

[@ginggung2413]

very nice job highlighting the usefulness and ease of use. Course I'd also love a piece xD #mcoding

[@spaghettihair]

You can set the pycharm debugger to break on exceptions!

[@igorb2216]

PyCharm licence you just said? I'm all in! #mcoding

[@codingjhames]

Thanks for the video James, it helps me so much with my game on pygame, and indeed Vim Debugging is a very painfull. #mcoding

[@plato4ek]

Woo-hoo! Another contest! #mcoding

[@ellipsiss]

Great work #mcoding Big time fan!

[@JaredJeyaretnam]

My only issue with debugging is that it’s super slow compared to running properly. I’m using Python to do physics computation so I normally do print debugging instead unless I absolutely have to! Also, I have no idea how to debug numba-jitted functions lol

[@Seun_O]

I learned something new. Thanks for the high quality content #mcoding

[@danielohara5749]

I just converted to an ide. I'm an old time coder and just used an editor. Ide found typos straight away. Took me a few days to realize I'll never go back.

[@luketurner314]

5:28 *ten items, it even tells you at the bottom with __len__; classic off-by-one error and again at 9:56 *eleven

[@ChristopherFerguson]

I always find your videos so helpful. Thanks so much! #mcoding

[@DarkosLab]

If I am 99% sure I know where and what the bug is I'll print debug to verify. But if im not sure where or why a bug is happening live debug is the way to go.

[@BrandonSolo]

I'#mcoding and debugging so much better thanks to this channel (padum tsssss)

[@Ayor88]

your videos are gold for self learner ! #mcoding

[@Yehonathanatos]

Thank you very muchly!!

[@talshafir10]

I love #mcoding videos!

[@sethdhanson]

Why are there comments in the .json file that vs code creates? If I try to put comments like that in my .json file, I get a warning they’re not permitted.

[@SBalajii]

Debugging is especially valuable when working with old code. print debugging is still fine in most of my hobby projects though.. #mcoding

[@XDjUanZInHO]

As always, going the other mile to show everything deeper than the surface level content #mcoding

[@brainforest88]

Nice. How do you like the new UI of PyCharm? #mcoding

[@PedigreeGuitars]

Thanks for all the great learning #mcoding