On 2/21/17 10:18, Tom Lane wrote: > Based on some not-fun I had along the way to that, I think it would be > a good idea to do the Python version check a bit earlier than you have > here. The shlib search in PGAC_CHECK_PYTHON_EMBED_SETUP is pretty fragile > and version-dependent, which means that a person could waste a lot of time > trying to get past the "could not find shared library for Python" error > before being told that their Python is too old. I propose to move the > minimum-version check into _PGAC_CHECK_PYTHON_DIRS, say right after the > [Python configuration directory] stanza. Unless there was some specific > reason for not wanting it to happen in python.m4?
It's fine to move it. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
