[egenix-users] mx.DateTime 3.2.x and numpy
mal at egenix.com
Tue Dec 20 16:27:56 CET 2011
Christian Marquardt wrote:
> thank you for the quick response!
> ----- "M.-A. Lemburg" <mal at egenix.com> wrote:
>> I'm not sure it's a bug. In mxDateTime 3.2 we replaced the old
>> coercion hack we'd been using in the days before our coercion
>> patches got integrated into Python, with the new methods.
>> Since the error is created by numpy, it looks like numpy is not
>> aware of the change. If there's something we can do to help,
>> let me know.
> I don't know much about the python core, so please apologize if my
> question is stupid - I just try to obtain some basic understanding
> so that I can follow this up further (if need be, with the numpy
> people). When talking about your coercion patches, are you talking
> about PEP 208? Didn't that go in in Python 2.1?
Yes, PEP 208.
> Besides, I believe numpy has its own coercion system...
We'll have to install numpy and check the problem. We may well have
to patch mxDateTime to make it work with numpy, if this uses its
own coercion mechanism.
Professional Python Services directly from the Source (#1, Dec 20 2011)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
::: Try our new mxODBC.Connect Python Database Interface for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
More information about the egenix-users