Ubuntu 16.04 LTS运行Python（含3.6）提示GLIBC_2.25未找到的原因

Let's break down the root causes of this common issue, since it pops up whether you're running the system-provided Python or your separate Python 3.6 installation:

• Your system's default GLIBC is too old
  Ubuntu 16.04 ships with GLIBC 2.23 as its core C library. The error message means the Python binary (or one of the libraries it’s trying to load) was compiled against GLIBC 2.25—a newer version than what your system has. GLIBC doesn’t support forward compatibility: programs built for a newer version can’t run on systems with an older GLIBC release.

• Your Python 3.6 wasn’t built for Ubuntu 16.04
  If you installed Python 3.6 using a precompiled binary (like from the official Python downloads page, or a third-party package/repo not targeted at 16.04), that binary was almost certainly compiled on a newer Ubuntu release (like 18.04, which uses GLIBC 2.27) or another distro with a more recent GLIBC. When you run this precompiled Python on 16.04, it can’t locate the newer GLIBC version it was linked against.

• Third-party C-extensions are triggering the error
  Even if your Python binary itself is compatible with Ubuntu 16.04, some Python packages (especially those with C extensions, like numpy, pandas, or cryptography) might have been installed as precompiled wheels built against GLIBC 2.25+. When Python tries to load these extensions at runtime, it hits the same missing GLIBC error. This is really common if you’re using pip to install packages without forcing source compilation.

内容的提问来源于stack exchange，提问作者Bruno