Hi, On February 14, 2022 12:48:12 PM PST, Tom Lane <t...@sss.pgh.pa.us> wrote: >Andres Freund <and...@anarazel.de> writes: >> On 2022-02-14 14:18:58 -0500, Tom Lane wrote: >>> Well, it's mid-February. Do we have a python2-removal patch >>> that's ready to go? > >> I can refresh mine. Iit might be good to first reapply >> f201da39edc - "Make configure prefer python3 to plain python." >> for a few days? > >We could I guess, but does it really buy anything? I'm sure that >some of the buildfarm still hasn't updated their Python installation, >but it'll be about the same failure we'd get from the final patch.
I guess what I was actually wondering about - but didn't write - was whether it's worth rejecting python 2 with just configure / msvc perl changes initially. The proper removal of python 2 support includes a bunch of buildsystem and code changes. Seems like it could be useful to have a snapshot of the buildfarm state after rejecting python 2, separate from the more verbose changes. Andres -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
