RFC: switching to python 3
ps_ml at gmx.de
Sun Jan 8 22:59:58 UTC 2012
Am 04.01.2012 15:12, schrieb Ralf Habacker:
> Am 04.01.2012 00:01, schrieb Patrick Spendrin:
>> Hi everybody,
>> we are currently thinking about switching emerge to python 3.X. This is
>> needed as the currently used version is not maintained anymore, there
>> will be no more 2.7.X release.
>> Our current plan is to get the python3 branch of emerge so far that we
>> can build KDE completely and then make the kde-4.8 branch the first one
>> to use python 3. From the users perspective, there won't be a lot of
>> changes, most package recipes will stay the same, only internal code
>> must be changed.
>> If you have some more ideas or comment please comment below, otherwise
>> we will try to switch in the coming few weeks before 4.8.0.
> The question is which internal code is required to change - in case it
> covers code which may need to be refactored because of other reasons, it
> may make sense to merge those part.
> There is for example the attempt to refactor the help page and command
> line processing (args.py) which has been paused because of design issues
> of the current implementation.
As far as I have seen it, only minor changes had to be done after the
2to3.py script had been run. These had been mostly related to subprocess
output (mostly for parsing git output). Since you probably don't parse
output of a subprocess in these refactorings, I don't think you would
have any problems at all. This should go into a branch, so we can easily
merge in all changes we make.
More information about the Kde-windows