That line is just an echo with some variables, so it should continue. If you know Make, then you can figure out that the failing target was bin/pip. Perhaps try the commands in the Makefile target bin/pip to see where it fails?
For this Training? No, but I would strongly recommend that you file an issue with the Training repository with the issue you found. It is more likely the authors will notice and improve the instructions.
For Plone in general, perhaps? We are in the process of improving the Install documentation, based on feedback.
it return error
/bin/python3: Error while finding module specification for 'import sys; print((int(sys.version_info[0]), int(sys.version_info[1])) > tuple(map(int, "3.8".split("."))))' (ModuleNotFoundError: No module named 'import sys; print((int(sys')
Yes. For new projects, it is a good idea to start with the latest Python.
I will also say that I had a similar issue as you with the detection of a supported Python version. I debugged this line:
Going from a fading memory, I found that that line returned an empty string for print((int(sys.version_info[0]), int(sys.version_info[1])). I cannot remember exactly what I did to fix it, but I think it had something to do with configuring pyenv to use the correct Python version so that this command in the Makefile would pull in the Python version I expected. Wish I had written it down now.
It was on my crusty 10-year old macBook Pro, but I don't remember the Python version I expected. This was not really a Python version thing, but something else about my environment. I recall that I backed up my ~/.bashrc, or maybe ~/.zshrc and other resource files, and started over from scratch. Something in there was hosing pyenv, preventing it from choosing the correct Python I wanted. Fortunately I rarely use that MBP, and only for travel, so I didn't care what I did to its environment.