https://bugs.freedesktop.org/show_bug.cgi?id=70196
Rene Engelhard <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|All |Other --- Comment #3 from Rene Engelhard <[email protected]> --- > I'm hesitant to consider this a bug as this patch was only intended for LO > versions using Python 3, but if Debian or other distributions are still > continuing to build LO 4.1+ UNO modules against Python 2, then yes, it's When LO 4.0 was released it explicitely was said that python2 was still supported "for a few releases", too, if people need it. "A few releases" of course is totally unclear - but the problem is that there's still loads of stuff out in the wild using pyUNO NOT (or Status unknown) ported. Even the most-used of it (unoconv) needed a patch from git (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707337) "python-openoffice" got fixed by removing it (;-)) and thus we still have #707338 [w|u| ] [bibus] please support python3 (and python3-uno) #707339 [w|u| ] [ooo2dbk] please support python3 (and python3-uno) #707340 [w|u| ] [docvert-libreoffice] please support python3 (and python3-uno) #707341 [w|u| ] [gnumed-client] please support python3 (and python3-uno) #707342 [w|u| ] [src:sqlkit] please support python3 (and python3-uno) reported by me in the Debian BTS... Otherwise I'd have stopped building python-uno, yes... I _know_ they are not working with stock LO 4.1+ and need to adapt, but... > certainly an issue. In that case, I'm also not entirely sure this will turn > > out to be the only Python 3-ism at this point in the code base. so far it is. > Two thoughts - first, as indicated in the Debian bug, removing the > with_traceback method call will be Python 2 compatible - but defeats the fix > > under Python 3. So not a good general purpose change, but it could be a > local distribution patch when building a Python 2 UNO module. Though pushing Yeah, that's I am doing now (see http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commitdiff;h=94dd0058eeb361cc16f824076da08062aebffec7;hp=eff512e1204010d9b0fb474d4d4bf12ea43928d9#patch4) > Alternatively, runtime version checking could be added for separate Python 2 > > and 3 code paths (I don't see a way to have a single path that works well > under Python 3 while simultaneously supporting 2). I can certainly produce a > > patch, but while likely modest, I don't currently have an LO build > environment to verify against Python 2. Is there any chance you might be > able to assist me with a quick sanity check of a patch under Python 2? As "quick" as a LO build is :-) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
