Date: prev next · Thread: first prev next last
2018 Archives by date, by thread · List index


Heya,

sorry for late reply, we had conference over a weekend and they blocked
all smtp ports...

Anyhow, currently for SUSE/openSUSE needs we are content with 2.7/3.4+

Actually even 3.4+ is acceptable for us.

Cheers

Tom

Michael Stahl píše v So 03. 03. 2018 v 19:50 +0100:
hi Tomáš,

is Python 2.6 support still needed for master / 6.1 ?

i'd like to bump the requirement to 2.7 if possible, it's really
painful
having to bother with 2.6 in this day and age...

On 02.03.2018 22:54, Thorsten Behrens wrote:
libreoffice-commits@lists.freedesktop.org wrote:
commit 44b4ad7d210097fdaed7dd94c5746b03f43592d3
Author: Thorsten Behrens <Thorsten.Behrens@CIB.de>
Date:   Fri Mar 2 22:38:18 2018 +0100

    build fix: disable gla11y for python 2.6


Some tinderboxen failing with:

Traceback (most recent call last):
File "/tinderbox/buildslave/source/libo-master/bin/gla11y", line
406, in main
       check_a11y_relation(filename, tree)
File "/tinderbox/buildslave/source/libo-master/bin/gla11y", line
255, in check_a11y_relation
       for obj in root.iter(´object´):
AttributeError: _ElementInterface instance has no attribute ´iter´

(for this new tool, it makes no sense to spend any effort getting it
to
run on 2.6, it's enough if it runs on developer's systems and none of
those are going to have python 2.6 on them)

Attachment: signature.asc
Description: This is a digitally signed message part


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.