displaysurf blit(oversurfoverrectdrawpresskeymsg(pygame display update(the game over screen is similar to the start screenexcept it isn' animated the words --game|and --over|are rendered to two surface objects which are then drawn on the screen pygame time wait( checkforkeypress(clear out any key presses in the event queue while trueif checkforkeypress()pygame event get(clear event queue return the game over text will stay on the screen until the player pushes key just to make sure the player doesn' accidentally press key too soonwe will put half second pause with the call to pygame time wait(on line (the argument stands for millisecond pausewhich is half of one second thencheckforkeypress(is called so that any key events that were made since the showgameoverscreen(function started are ignored this pause and dropping of the key events is to prevent the following situationsay the player was trying to turn away from the edge of the screen at the last minutebut pressed the key too late and crashed into the edge of the board if this happensthen the key press would have happened after the showgameoverscreen(was calledand that key press would cause the game over screen to disappear almost instantly the next game would start immediately after thatand might take the player by surprise adding this pause helps the make the game more --user friendly|drawing functions the code to draw the scorewormappleand grid are all put into separate functions def drawscore(score) scoresurf basicfont render('score% (score)truewhite scorerect scoresurf get_rect( scorerect topleft (windowwidth displaysurf blit(scoresurfscorerectthe drawscore(function simply renders and draws the text of the score that was passed in its score parameter on the display surface object email questions to the authoral@inventwithpython com