[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Making pology python3 compatible
From:       Shinjo Park <kde () peremen ! name>
Date:       2019-06-12 18:07:39
Message-ID: 4580274.smY2hygtx7 () ainazi
[Download RAW message or body]

2019년 6월 10일 월요일 오후 5시 55분 51초 CEST에 Adrián Chaves 님이 쓴 글:
> I wonder how well would 2to3 (https://docs.python.org/2/library/2to3.html)
> work on the Pology codebase.
> O luns, 10 de xuño de 2019 17:48:44 CEST Albert Astals Cid escribiu:
> > the python 2 clock runs out in 6 months.
> > 
> > Trying to run pology with python3 doesn't work.
> > 
> > Has anyone explored how hard would it make it to be compatible with both?
> > Worst case scenario the l10n.kde.org machine seems to have python 3.5,
> > which seems almost every other distro ships
> > (https://repology.org/project/python3/badges) so requiring python 3.5
> > wouldn't be that terrible either.
> > 
> > Cheers,
> > 
> >   Albert

I tested a blind conversion of 2to3 and execution didn't worked well (also 
gave minor warnings). Running posieve on 2to3-processed files gave errors on 
pology/colors.py, possibly due to str/unicode changes and separation on py3. 
Any other parts utilizing string needs to be examined, especially decode() and 
encode() calls.

Another possibly related question: do we have some test suite for pology (I 
couldn't find it)? Even if someone manages the conversion of pology to Python 
3, it is also needed to make sure that Python 3 version of pology works the 
same as before.


[prev in list] [next in list] [prev in thread] [next in thread]