--without-python does not work for 9.11.13

[Dennis Clarke]

If one tries to build 9.11.13 with ( or without ) --without-python then
the build fails in multiple ways :

.
.
.
gmake[2]: Leaving directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/confgen'
making all in 
/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python
gmake[2]: Entering directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python'
making all in 
/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python/isc
gmake[3]: Entering directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python/isc'
making all in 
/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python/isc/tests
gmake[4]: Entering directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python/isc/tests'
gmake[4]: Leaving directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python/isc/tests'
/usr/local/bin/python3.7 policy.py parse /dev/null > /dev/null
Fatal Python error: initfsencoding: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'

Current thread 0x0000000000000001 (most recent call first):
/usr/local/bin/bash: line 1: 15637 Abort                   (core dumped) 
/usr/local/bin/python3.7 policy.py parse /dev/null > /dev/null
gmake[3]: *** [Makefile:441: parsetab.py] Error 134
gmake[3]: Leaving directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python/isc'
gmake[2]: *** [Makefile:132: subdirs] Error 1
gmake[2]: Leaving directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin/python'
gmake[1]: *** [Makefile:79: subdirs] Error 1
gmake[1]: Leaving directory 
'/usr/local/build/bind-9.11.13_Oracle_sparc64vii+.001/bin'
gmake: *** [Makefile:88: subdirs] Error 1


The above happens regardless which direction you choose.

Yes Python is available.  Yes it is in the path.

beta$ $PYTHON --version
Python 3.7.4
beta$ echo $PYTHON
/usr/local/bin/python3.7
beta$

Regardless which direction a person jumps this python trash gets created
  during configure :

config.status: creating bin/python/Makefile
config.status: creating bin/python/isc/Makefile
config.status: creating bin/python/isc/utils.py
config.status: creating bin/python/isc/tests/Makefile
config.status: creating bin/python/dnssec-checkds.py
config.status: creating bin/python/dnssec-coverage.py
config.status: creating bin/python/dnssec-keymgr.py
config.status: creating bin/python/isc/__init__.py
config.status: creating bin/python/isc/checkds.py
config.status: creating bin/python/isc/coverage.py
config.status: creating bin/python/isc/dnskey.py
config.status: creating bin/python/isc/eventlist.py
config.status: creating bin/python/isc/keydict.py
config.status: creating bin/python/isc/keyevent.py
config.status: creating bin/python/isc/keymgr.py
config.status: creating bin/python/isc/keyseries.py
config.status: creating bin/python/isc/keyzone.py
config.status: creating bin/python/isc/policy.py
config.status: creating bin/python/isc/rndc.py
config.status: creating bin/python/isc/tests/dnskey_test.py
config.status: creating bin/python/isc/tests/policy_test.py

Whomever came up with the idea to embed python inside ISC Bind is
someones cousin that can't find a job elsewhere? Who let this happen?
To pure beautiful cross platform clean C code someone allowed python
in the door?

Has anyone tested this "--without-python" option ?




-- 
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional