Sure, many of us have worked on calendars / schedulers and are familiar with pytz. What's your specific question, that's not already well answered in the SO question you point to and ITS answers / comments...?
Edit: so there are no special, particular pitfalls if you do things as recommended in the best answers to the other question. In particular, do standardize on UTC internally ("GMT" is an antediluvian term and concept) and convert to/from timzones (w/DST &c) on I/O (just as you should standardize on Unicode internally and encode/decode to bytes, if you must, only on I/O!-).
There's a simple and flexible module in the Python standard library called sched which provides a configurable "event scheduler" and might be at the core of your app, with help from calendar, datetime etc. Some of the recipes in the "Time and Money" chapter of the Python Cookbook, 2nd ed, may help (it's widely available as online pirate copies, though as a co-author I don't necessarily LIKE that fact;-).
It's hard to say much more without having any idea of what you're writing -- web service, web app, desktop app, or whatever else. Do you want to support vCal, iCalendar, vCalendar, other forms of interop/sync/mashup and if so with what other apps, services and/or de facto standards? Etc, etc -- like all apps, it can grow and grow if it proves successful, of course;-).