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

List:       kwrite-devel
Subject:    Re: Review Request: Tidy up Python 3 support.
From:       Shaheed Haque <srhaque () theiet ! org>
Date:       2012-11-21 11:23:58
Message-ID: CAHAc2jcsub1T7x+t33bLiSBngH0iwY5oCEK8eBdq+OosO6v2cQ () mail ! gmail ! com
[Download RAW message or body]

@domink, while the diff is certainly VERY nasty to cover all the cases
(and the documentation is, a bit hazy around the UCS-2/UTF-16 thing),
I'd prefer to cover the bases if I can. I think it is possible, though
all the Googling didn't show a clean solution anywhere that I could
steal :-).

@Luca: if you can tell me how to make the Kate build pick up alternate
Python setups, I could do better testing myself, at least with the
options that Ubuntu has available.

On 21 November 2012 10:29, Luca Beltrame <einar@heavensinferno.net> wrote:
> In data mercoledì 21 novembre 2012 11:25:06, Dominik Haumann ha scritto:
>
> Hello Dominik,
>
>> without knowing too much details, but imo supporting all possible Python
>> versions sounds like a maintanence hell.
>
> *Usually* there aren't such major breakages of the C API. Plenty of projects
> of significant size (Numpy/Scipy to name one) manage support of both versions
> in the same codebase.
>
> IOW, I'm sure we can find an API that works with all 3.x versions. I noticed
> the error in the RR but I did not have time to investigate why and how to fix
> it. I probably can this weekend, though.
>
>> What about simply requiring Python 3.3 (and, if really necessary, 2.x)?
>
> Hmm... Dropping support for 2 is a no-go at the moment IMO because there is
> still a lot that was not ported to 3.
>
> --
> Luca Beltrame - KDE Forums team
> KDE Science supporter
> GPG key ID: 6E1A4E79
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

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