Re: [SQLObject] Proposed Plan for Porting to Python 3

[Ian C. <gra...@gm...>]

On Thu, Dec 11, 2014 at 8:13 AM, Ian Cordasco
<gra...@gm...> wrote:
> Awesome!
>
> On Dec 11, 2014 8:10 AM, "Oleg Broytman" <ph...@ph...> wrote:
>>
>> On Wed, Dec 10, 2014 at 12:55:36AM +0100, Oleg Broytman <ph...@ph...>
>> wrote:
>> > create a separate branch for 2.0. Then master will be free for working
>> > on Py3 compatibility.
>>
>>    Done: I created a new branch 2.0 and edited master to be 3.0
>> pre-alpha.
>>
>>    Ian, the master is waiting for you! ;-)
>>
>> Oleg.
>> --
>>      Oleg Broytman            http://phdru.name/            ph...@ph...
>>            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
>> sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss


So I finally got some time. I've put together
https://github.com/sqlobject/sqlobject/pull/1 so we can have something
that everyone can reproduce with. It's uncovered a couple bugs in the
tests (specifically around depending on hash/dictionary ordering).
That aside, there are a bunch of problems pyflakes has with the
code-base but just running the py34 version has found syntactical
incompatibilities that should be easy to fix. I'd like to do that in a
separate pull request.

I'd like everyone's thoughts on this. This particular strategy is
something a lot of projects are beginning to use. I feel like we
should also add some documentation around running the tests
(especially for people who don't deal with postgres often (like me)
;)).

Cheers,
Ian