Re: [SQLObject] Python 3 and FormEncode

[Oleg B. <ph...@ph...>]

On Mon, Jul 25, 2016 at 02:51:03PM +0200, Christoph Zwerschke <ci...@on...> wrote:
> Am 25.07.2016 um 13:18 schrieb Oleg Broytman:
>  >   File "<stdin>", line 1, in <module>
>  > NameError: name 'unicode' is not defined
> 
> Hi Oleg,
> 
> FormEncode 1.3 should run with Python 3, it uses 2to3. This error 
> indicates that during installation the 2to3 tool did not run properly. 
> Some have reported that this problem can be caused by cached wheels.
> 
> In FormEncode 2, 2to3 is not used any more because of such issues, but I 
> think there is no official release of FormEncode 2 yet.
> 
> Anyway, if FormEncode 1.3 is installed properly, it should work.
> 
> -- Christoph

   Thank you very much! That increases assurance in our tests.

   I've used star-destroyer to fix `import *`, fixed some tests manually
and need to be sure I didn't break anything, so I ran tests with Python
2.7 and 3.4 -- and oops, got these problems with FormEncode.
   Now with FormEncode from git repo I can run tests -- and already
caught a minor bug.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.