Might be worth it to put `python3.9 python3.8` there as well?
Created attachment 196258 [details] auto-configure patch
Created attachment 196259 [details] Sub in the correct python binary name History shows pretty clearly that I will keep forgetting to add in new py3 versions, so I'd like to take that necessity out of the picture entirely. Can you try out this instead? It determines the binary name for the current python version and just subs that in instead.
It does seem to work perfectly well: checking --with-python3-command argument... no checking for python3.7... /usr/local/bin/python3.7 checking Python version... 3.7 Poudriere builds the package successfully and I am sure it will work fine. Thank you.
A commit references this bug: Author: adamw Date: Thu Aug 16 21:04:02 UTC 2018 New revision: 477376 URL: https://svnweb.freebsd.org/changeset/ports/477376 Log: Improve the way vim looks for python binaries Previously, we patched in the names of all the python binary versions, but I have been doing a terrible job of keeping them up-to-date. Instead, just tell vim's configure script the path to the binary we're using. This will fix building against python 3.7. PR: 230675 Reported by: Kamigishi Rei MFH: 2018Q3 Changes: head/editors/vim/Makefile head/editors/vim/files/patch-src-auto-configure
Thank you for including the configure output! I just used --with-python3-command (and was able to do the same thing with --with-python-command). I feel much better about not having to worry about forgetting to update the list again (which I can absolutely guarantee was going to happen). Because this is a build fix, I've requested an MFH.
Just FTR I decided against the MFH. Merging r476013 will touch over 200 ports, and python37 isn't in 2018Q3 anyway.