Logged In: YES 
user_id=38388

Well, this may sound easy, but once you get into timezones things start to become one big can of worms, e.g. 
just have a look at how daylight savings time is handled in different countries of the world or how time zone names 
sometimes map to multiple different zones. 

OTOH, numeric timezones are easy to handle and all that is needed is some simple code to convert a ticks value 
plus an offset to a nice ISO string representation an vice-versa. That should be easy to add to the time module...

About adding mxDateTime to the core: I suppose it's simply too big. Also, I have a slightly different way of 
maintaining the mx tools than what is considered the Python way -- I usually happily add new features and 
modules without much fuzz; wouldn't want to have to write a PEP to enhance my own stuff ;-)

As compromise, I could add some ISO date/time parsing and formatting code from mxDateTime to Python 2.3.