Re: [SQLObject] Python 3 and FormEncode

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

On Mon, Jul 25, 2016 at 7:55 AM, Ian Cordasco
<gra...@gm...> wrote:
> On Mon, Jul 25, 2016 at 7:51 AM, 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.
>
> So this is because FormEncode 1.3 claims it can provide a universal
> wheel (https://github.com/formencode/formencode/blob/1.3.0/setup.cfg#L29)
> but it cannot. A 1.3.1 release should be provided with universal = 0.
> This way when pip caches the wheel it produces, it tags it with py2 or
> py3 as appropriate.

I submitted https://github.com/formencode/formencode/issues/117 to see
if we can alleviate this.