During configure, newt will blindly assume there's ${PYTHONVERS}-config command without testing.

version: newt-0.52.14

In Makefile.in, about line 79:

_snackmodule.so:   snackmodule.c $(LIBNEWTSH)                                                                                 
    [ -n "$(PYTHONVERS)" ] && for ver in $(PYTHONVERS) ; do \
            mkdir -p $$ver ;\
            PCFLAGS=`$$ver-config --cflags`; \
            PIFLAGS=`$$ver-config --includes`; \
            PLDFLAGS=`$$ver-config --ldflags`; \
            PLFLAGS=`$$ver-config --libs`; \
            $(CC) $(CPPFLAGS) $$PIFLAGS $$PCFLAGS -c -o $$ver/snackmodule.o snackmodule.c ;\
            $(CC) --shared $$PLDFLAGS $$PLFLAGS $(LDFLAGS) -o $$ver/_snackmodule.so $$ver/snackmodule.o -L.  -lnewt $(LIBS);\
    done || :
    touch $@

The Python version recognized by the configure script is `python2.7`, but there's only `python-config-2.7` command in my system (Gentoo Linux), no `python2.7-config` available.

In this situation, I suggest we should test if `python2.7-config` exists. If not, we should provide a warning information and use `python-config` instead.