On Sun, Dec 07, 2014 at 08:06:29AM +0100, Oleg Broytman <p...@phdru.name> wrote: > MySQL doesn't support microseconds until 5.6.4, Travis runs > 5.5, so the error can be ignored. > I will work on skipping the test on backends that don't support > microseconds and adapt SQLObject to MySQL 5.6.4+ (date/time columns must > be created with precision: TIME(6) instead of TIME and so on).
Done, all tests are now passed, see https://travis-ci.org/sqlobject/sqlobject/branches I added the test status images at PyPI, see https://pypi.python.org/pypi/SQLObject/1.5.4 https://pypi.python.org/pypi/SQLObject/1.6.2 https://pypi.python.org/pypi/SQLObject/1.7.0 https://pypi.python.org/pypi/SQLObject/2.0.0a2dev-20141028 Need to add them to the docs. There is one sporadic bug related to round number of microseconds like 83500: some parts of code think it's 0.0835 (83500), and some think it's 0.835 (835000). See the traceback near the end of https://travis-ci.org/sqlobject/sqlobject/jobs/42989776 I hope to fix the bug. Then I'm going to release 2.0 beta 1 and create a separate branch for 2.0. Then master will be free for working on Py3 compatibility. Oleg. -- Oleg Broytman http://phdru.name/ p...@phdru.name Programmers don't die, they just GOSUB without RETURN. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss