On 2008-1119 11:15:52, D'Arcy J.M. Cain wrote: > I am wondering about this code. > > try: # use mx.DateTime module if available > from mx.DateTime import DateTime, \ > TimeDelta, DateTimeType > except ImportError: # otherwise use standard datetime module > from datetime import datetime as DateTime, \ > timedelta as TimeDelta, datetime as DateTimeType > > Does mx.DateTime give us anything that the standard module doesn't? If > not I would like to get rid of it rather than depending on a third > party package to build ours.
why don't you turn it the other way round? use datetime if it's there and fall back to mx if datetime is not present... as far as I can tell, mx is only needed in the Python2.1 systems still in circulation, which is possibly quite a few... just to make an example: if you live inside ArcGis 9.1... don't know how much work it would be, but I think it would also be nice if inside of the module one would see the names as defined in the standard module, instead of the mx names... regards, Mario -- If we knew what we were doing, it wouldn't be research. _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
