Hi Jim, Am 23.04.20 um 13:42 schrieb Jim Jagielski: > I agree. We should ensure that all works w/ 2.7.18 since it is the last of > the Python 2.7s... even if it means we "fix" AOO to work with it, we should > simply baseline that version. In trunk and AOO42X we are already on 2.7.17. No problems so far.
But in 4.1.7 we still ship 2.7.6 (?). Regards, Matthias > >> On Apr 21, 2020, at 7:56 AM, Matthias Seidel <[email protected]> >> wrote: >> >> Hi all, >> >> The final Python 2.7.18 is out: >> >> https://www.python.org/downloads/release/python-2718/ >> >> I would expect no major changes to 2.7.17, so we could probably update >> to that version? >> >> Regards, >> >> Matthias >> >> Am 02.01.20 um 03:30 schrieb Pedro Giffuni: >>> Hello AOO devs and best wishes for the New Year! >>> >>> Well ... time has passed and Python 2 is now deprecated! >>> >>> I have a patch here to update AOO 4.2's version of Python to the latest >>> (perhaps last) release in that line: >>> >>> http://people.apache.org/~pfg/patches/patch-python-2.17.diff >>> >>> This is a remake of the previous update that I had made for >>> cpython-2.16, but which no one tested ! I currently lack an AOO setup >>> with git so please someone else will have to test and commit. >>> >>> On the near term, we really should update to Python 3, but that will be >>> challenging for the build system since it requires a newer version of >>> the MS compiler. >>> >>> Building with an external python is also currently broken for python >>> versions >= 3.6. >>> >>> Regards, >>> >>> Pedro. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
smime.p7s
Description: S/MIME Cryptographic Signature
