[Libreoffice] [PUSHED] Python 3 compatibility for build tools + unicode support for filters

Michael Meeks <michael.meeks -AT- novell.com>
Mon, 04 Apr 2011 15:19:47 +0100


On Mon, 2011-04-04 at 11:38 +0100, Michael Meeks wrote:

      Code looks lovely :-) I had a read / test of it and a great improvement
- thanks !.


        Pushed ! :-) excited to see what is next; can we switch to an internal
python 3.0 ? [ no doubt it will break an extension or two that is
written in old-style python, but ... perhaps we should do that what do
you think ? ].

        ATB,

                Michael.

-- 
 michael.meeks@novell.com  <><, Pseudo Engineer, itinerant idiot

Context

[Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · archlid
- Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · archlid
  - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Michael Meeks
    - [Libreoffice] [PUSHED] Python 3 compatibility for build tools + unicode support for filters · Michael Meeks
  - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Caolán McNamara
    - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Michael Meeks
      - Re: [Libreoffice] [Patch] Python 3 compatibility for build tools + unicode support for filters · Andreas Becker

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.