For my PyCon tutorials over the years, I settled on an approach which is hands-on, broken into sections containing steps or tasks. Each step has an extensive writeup done in Sphinx, with working code for the results of each step available in GitHub. The writeup details the work to do, followed by an analysis section, and an extra credit section (for those that go fast). On each step, I demo what’s to be done, you do it, then we chit-chat when everyone is complete.
It’s a nice way to go through a lot of material fast, without leaving anybody behind. But it takes a LOT of preparation, much more than the normal “8 hours of prep for each hour of class time” rule.
So to give a good taste of why the tutorial is worth attending, here is the current material. I’m at the 2.5 (estimated) mark, so the sections starting with “Debugging” are where I will put in effort beyond the minimum, so to speak. I also need to do another pass through, bullet-proofing things. Finally, I’d like to do a better job of linking to PyCharm help topics and Python/Flask help material. Afterwards, I might try to do screencasts of each section, so people can self-serve on the tutorial.
If you’d like to do the tutorial, please do the “Setup” step in advance. We (the PyCharm team) will be in the hallways 20 or so minutes before start time to help people if needed, to try and save classroom time. If you have any questions or just want to say hi, come by our PyCharm booth on Monday or Tuesday. We’d love to see you.
I have to say, it feels good going to EuroPython again. I went to the first two in Charleroi, the next two in Göteborg. Bilbao should be a lot of fun.