On Mon, Apr 28, 2014 at 8:16 AM, Thomas Goirand <z...@debian.org> wrote: > On 04/28/2014 06:16 PM, Osamu Aoki wrote: >> Hi, >> >> Questions are how Debian Jessie packages should be packaged with regards >> to configuration choices etc.: >> >> wayland support or not (I am skipping ones using libwayland-dev now) >> python3 support or not (Are we moving too?) >> X session autostart scripts under systemd > > I'm not sure about the other components, but I'm convinced that we > should try as much as possible to support Python 3. It has been released > in 2008, and upstream (for Python) is pushing for its adoption, and > would like to deprecate Python 2. Sure, we wont deprecate Python 2 for > Jessie, however, it seems reasonable to try to push for Python 3 > adoption as well, and this means trying to package Python module with > Python 3 support as much as possible. > > Whenever possible, pushing Python 3 patches upstream is also a good > idea, IMO. > > Thomas > Hello,
There was a discussion on the Debian Python lists about removing python2 from the default installation (including the standard task). The main roadblock in doing so was the reportbug package and its dependencies. After much hard work I was unable to get suds (the only SOAP library supporting python3) to make the requests that the BTS required. The main issue was with the way the BTS defined "arrays". What it accepts as arrays are not arrays in SOAP but look much more like the way you pass a list to a function in Perl. Until this issue can be resolved, either by porting the existing unmaintained SOAP library the python-debianbts module uses or making changes the BTS SOAP interface, python2 in the standard installation is here to stay. Regards, Jordan Metzmeier -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cad758rju7o0j2mvk06aan5muve4ohgglpfc1gzubqragdd1...@mail.gmail.com
