I'm not all that patient with tutorials. I like to be bombarded with short phrases and execution of code and their results with explanations as to why they work. More often than not allegories are used (and I'm probably guilty of this) that really don't help me understand, it in action works a lot better for me. For the most part I was looking for one quick thing in these tutorials, how to get text printed out and it took me scavanging through a few tutorials.
It's less their fault and more my fault for wanting something simple that usually comes later in explanations. Skipping to those parts in some often involved missing vital initialization code that they mention in the their python primer. Beyond that I've found system incompatibilities for some odd reason. Either way I have managed to get some of it working.
The other thing that may prove to be a problem is the need for pygame instillation. I had a bit of a problem with it myself but after some trial and error I got it to work. This is not a thing I like at all considering my preferred ideas with python being self contained. Though I may be able to keep the source code in with the game archive to allow use of the game without need for instillation, I am not fully sure though.
This is more or less prep work for a traditional roguelike I'm going to try and get up running soon, but that's going to be after a probably anticlimatic Project Combat Test release. I'm still going to finish that sometime soon and hopefully life won't get in the way of my two week pseudo deadline.