[DB-SIG] Re: DCOracle2 Installation Issues on Linux Redhat 7.4

[M.-A. Lemburg]

Kevin Jacobs wrote:
> On Tue, 11 Feb 2003, M.-A. Lemburg wrote:
> 
>>>You may also need to add:
>>>
>>>http://www.lemburg.com/files/python/mxDateTime.html
>>
>>That would be good news, but I'm afraid the DateTime module
>>is the one from Zope and not mxDateTime.
> 
> Speaking of which -- now that Python is poised to grow an official DateTime
> classes, what are your thoughts on revising DB-API to officially endorse
> them?  Don't get me wrong; I use mx.DateTime and think it is a great product
> and very much appreciate that you make it available.  However, it does make
> sense to move toward using a builtin Python class in DB-API.  These can then
> be trivially converted to mx.DateTime objects (as long as leap seconds
> aren't a big deal).

Why should leap seconds matter ?

> Your thoughts?

I can add them to the PEP, if that should matter.

However, you should know that the datetime module in Python 2.3 does
not provide a C API of its own, so integration with C code is not as
easy as with mxDateTime. And, of course, the datetime module is
not available in Python 1.5.2 - 2.2.

-- 
Marc-Andre Lemburg
eGenix.com

Professional Python Software directly from the Source  (#1, Feb 11 2003)
 >>> Python/Zope Products & Consulting ...         http://www.egenix.com/
 >>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/
________________________________________________________________________
Python UK 2003, Oxford:                                     49 days left
EuroPython 2003, Charleroi, Belgium:                       133 days left