veyepar: A-hunting We Will Go: Debugging pytest with Django

Author(s):	Cris Ewing
Location	Mystic Theatre
Date	nov Sun 03	Days Raw Files
Start	16:30	First Raw Start	16:03
Duration	0:30:0	Offset	0:26:46
End	17:00	Last Raw End	17:33
Chapters	00:00 0:29:00
Total cuts_time	31 min.

https://2019.northbaypython.org/schedule/presentation/7/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Ahunting_We_Will_Go_Debugging_pytest_with_Django.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Debugging code is a skill we all must learn, but one that is rarely taught particularly well. We speak about “reading the traceback” as if that alone is sufficient to lead us to the solution to all our problems. But what happens when it isn’t enough? When the traceback is the symptom of a problem that happened elsewhere, or elsewhen? How do you approach debugging when the leads are slim?

This talk presents the tools of debugging couched in a very specific tale of a particular bug hunt. The specific bug is a good one because it presents a number of the classic tough problems in debugging. It starts with an intermittent failure. It has a traceback that is completely remote from the actual cause of the problem. It involves the interaction of three separate systems: a web framework, a test framework, and a database. And in the end, the cause is so small, and the solution so simple, that it serves to remind us all to be humble in the face of the complexity we deal in daily.

During this talk, you'll learn about ways to use printing and logging as well as pdb.  You'll see how core Python tools like dbapi2 and the inspect module can help to solve common problems. You'll learn how to spot new avenues for exploration, and how to figure out when you're in a blind alley.

The talk is entertaining for folks of any level, but it’s probably of most use to beginner and intermediate programmers.

So you’ve got a bug and you can’t see where to begin? Well, let me tell you, I’ve been there. Have a seat and I'll tell you a story of a bug that cost me three days and ended in three lines of code. I promise you’ll laugh, you’ll cry, and when we’re finished, you might see a path to start your own hunt.

Comment:

production notes