Enable python3.

Enable python3.

The default is to use 'python' and --with-python option can change it.
./configure --with-python=python3 .

[Peng, 2014-01-23 12:20:06]

On 2014/01/23 10:31:39, fujiwara wrote:
Can not see diff. Please re-upload it.

[fujiwara, 2014-01-24 02:07:14]

On 2014/01/23 12:20:06, Peng wrote:
> On 2014/01/23 10:31:39, fujiwara wrote:
> Can not see diff. Please re-upload it.

Uploaded again.
I think unichr() is not needed in this code.

[Peng, 2014-01-24 02:43:37]

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py
File engine/engine.py (right):

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode21
engine/engine.py:21: import enchant
I think it is better import __future__ in every files which use the python3
features.

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode91
engine/engine.py:91: keyval in range(keysyms.A, keysyms.Z + 1):
why change to range?

https://codereview.appspot.com/55990043/diff/20001/engine/main.py
File engine/main.py (right):

https://codereview.appspot.com/55990043/diff/20001/engine/main.py#newcode20
engine/main.py:20: 
same. import __future__

[fujiwara, 2014-01-27 04:22:47]

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py
File engine/engine.py (right):

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode21
engine/engine.py:21: import enchant
On 2014/01/24 02:43:37, Peng wrote:
> I think it is better import __future__ in every files which use the python3
> features.

Added __future__.
But I still don't think it's not needed because we won't maintain python2 and
continue to use the python3 format, make sure the double quoted sentence.

Other migration does not use __future__.
https://wiki.gnome.org/Initiatives/GnomeGoals/Python3Porting

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode91
engine/engine.py:91: keyval in range(keysyms.A, keysyms.Z + 1):
On 2014/01/24 02:43:37, Peng wrote:
> why change to range?

Because it does not work in python3.
Try 2to3 which is included in python3-tools package in Fedora.
http://python3porting.com/

https://codereview.appspot.com/55990043/diff/20001/engine/main.py
File engine/main.py (right):

https://codereview.appspot.com/55990043/diff/20001/engine/main.py#newcode20
engine/main.py:20: 
On 2014/01/24 02:43:37, Peng wrote:
> same. import __future__

I added it but I don't think we need it because we won't maintain python2.

[Peng, 2014-01-27 18:49:09]

On 2014/01/27 04:22:47, fujiwara wrote:
> https://codereview.appspot.com/55990043/diff/20001/engine/engine.py
> File engine/engine.py (right):
> 
> https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode21
> engine/engine.py:21: import enchant
> On 2014/01/24 02:43:37, Peng wrote:
> > I think it is better import __future__ in every files which use the python3
> > features.
> 
> Added __future__.
> But I still don't think it's not needed because we won't maintain python2 and
> continue to use the python3 format, make sure the double quoted sentence.
> 
> Other migration does not use __future__.
> https://wiki.gnome.org/Initiatives/GnomeGoals/Python3Porting
> 
> https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode91
> engine/engine.py:91: keyval in range(keysyms.A, keysyms.Z + 1):
> On 2014/01/24 02:43:37, Peng wrote:
> > why change to range?
> 
> Because it does not work in python3.
> Try 2to3 which is included in python3-tools package in Fedora.
> http://python3porting.com/
> 
> https://codereview.appspot.com/55990043/diff/20001/engine/main.py
> File engine/main.py (right):
> 
> https://codereview.appspot.com/55990043/diff/20001/engine/main.py#newcode20
> engine/main.py:20: 
> On 2014/01/24 02:43:37, Peng wrote:
> > same. import __future__
> 
> I added it but I don't think we need it because we won't maintain python2.

lgtm

[Peng, 2014-01-27 18:49:18]

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py
File engine/engine.py (right):

https://codereview.appspot.com/55990043/diff/20001/engine/engine.py#newcode21
engine/engine.py:21: import enchant
On 2014/01/27 04:22:47, fujiwara wrote:
> On 2014/01/24 02:43:37, Peng wrote:
> > I think it is better import __future__ in every files which use the python3
> > features.
> 
> Added __future__.
> But I still don't think it's not needed because we won't maintain python2 and
> continue to use the python3 format, make sure the double quoted sentence.
> 
> Other migration does not use __future__.
> https://wiki.gnome.org/Initiatives/GnomeGoals/Python3Porting

At least if will forbid that IME developers use python2 style print in their
IMEs based on ibus-tmpl. It will save our efforts for fixing thrid-party IMEs
later.