Thread: [SQLObject] something for the 0.6.1 release notes
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
From: Kevin D. <da...@gm...> - 2005-02-05 18:07:05
|
Hi, I just installed SQLObject 0.6.1 and noticed a bunch of my unit tests failing on date-related tests (gotta love automated tests :). It looks like the default datetime implementation has changed from mxDateTime to datetime. That suits me just fine, but it is a breaking change that is worth mentioning in the release notes, I think. Kevin |
From: Oleg B. <ph...@ma...> - 2005-02-05 18:31:41
|
On Sat, Feb 05, 2005 at 01:07:02PM -0500, Kevin Dangoor wrote: > I just installed SQLObject 0.6.1 and noticed a bunch of my unit tests > failing on date-related tests (gotta love automated tests :). It looks > like the default datetime implementation has changed from mxDateTime > to datetime. Yuo can change it back in your program: from sqlobject import col if col.mxdatetime_available: col.default_datetime_implementation = col.MXDATETIME_IMPLEMENTATION before your table definitions. Oleg. -- Oleg Broytmann http://phd.pp.ru/ ph...@ph... Programmers don't die, they just GOSUB without RETURN. |
From: Kevin D. <da...@gm...> - 2005-02-05 19:45:32
|
On Sat, 5 Feb 2005 21:31:33 +0300, Oleg Broytmann <ph...@ma...> wrote: > On Sat, Feb 05, 2005 at 01:07:02PM -0500, Kevin Dangoor wrote: > > I just installed SQLObject 0.6.1 and noticed a bunch of my unit tests > > failing on date-related tests (gotta love automated tests :). It looks > > like the default datetime implementation has changed from mxDateTime > > to datetime. > > Yuo can change it back in your program: Certainly... I had spotted that in col.py. I was just pointing out that this was a breaking change to default behavior, which is usually a nice thing to drop in the release notes. Kevin |