diff --git a/.gitignore b/.gitignore
index 97dbc43a2cee7..6700e4172e80d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -30,8 +30,50 @@ coverage.xml
 # Test output
 /out/
 
-# All the ps1 files are generated by bootstrap...
+# Windows ps1 launchers (created by ./tools/maint/create_entry_points.py)
 *.ps1
 # ...except the templates.
 !/tools/run_python.ps1
 !/tools/run_python_compiler.ps1
+
+# Shell scripts (created by ./tools/maint/create_entry_points.py)
+em-config
+emar
+embuilder
+emcmake
+emconfigure
+emdump
+emdwp
+emmake
+emnm
+emprofile
+emranlib
+emrun
+emscan-deps
+emscons
+emsize
+emstrip
+emsymbolizer
+tools/file_packager
+tools/webidl_binder
+
+# Windows .bat files (created by ./tools/maint/create_entry_points.py)
+em-config.bat
+emar.bat
+embuilder.bat
+emcmake.bat
+emconfigure.bat
+emdump.bat
+emdwp.bat
+emmake.bat
+emnm.bat
+emprofile.bat
+emranlib.bat
+emrun.bat
+emscan-deps.bat
+emscons.bat
+emsize.bat
+emstrip.bat
+emsymbolizer.bat
+tools/file_packager.bat
+tools/webidl_binder.bat
diff --git a/bootstrap b/bootstrap
index eef0f00c6730f..16710c6c5cf88 100755
--- a/bootstrap
+++ b/bootstrap
@@ -11,8 +11,8 @@
 # To make modifications to this file, edit `tools/run_python.sh` and then run
 # `tools/maint/create_entry_points.py`
 
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
+# $PYTHON -E does not ignore _PYTHON_SYSCONFIGDATA_NAME, an internal of cpython
+# used in cross compilation via setup.py, so we unset it explicitly here.
 unset _PYTHON_SYSCONFIGDATA_NAME
 
 if [ -z "$PYTHON" ]; then
diff --git a/cmake/Modules/Platform/Emscripten.cmake b/cmake/Modules/Platform/Emscripten.cmake
index 494c8169ff3ec..16659859a946d 100644
--- a/cmake/Modules/Platform/Emscripten.cmake
+++ b/cmake/Modules/Platform/Emscripten.cmake
@@ -60,7 +60,7 @@ endif()
 # Locate where the Emscripten compiler resides in relative to this toolchain file.
 if (NOT DEFINED EMSCRIPTEN_ROOT_PATH)
   get_filename_component(GUESS_EMSCRIPTEN_ROOT_PATH "${CMAKE_CURRENT_LIST_DIR}/../../../" ABSOLUTE)
-  if (EXISTS "${GUESS_EMSCRIPTEN_ROOT_PATH}/emranlib")
+  if (EXISTS "${GUESS_EMSCRIPTEN_ROOT_PATH}/emranlib.py")
     set(EMSCRIPTEN_ROOT_PATH "${GUESS_EMSCRIPTEN_ROOT_PATH}")
   else()
     # If not found by above search, locate using the EMSCRIPTEN environment variable.
diff --git a/em-config b/em-config
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/em-config
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/em-config.bat b/em-config.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/em-config.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emar b/emar
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emar
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emar.bat b/emar.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emar.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/embuilder b/embuilder
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/embuilder
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/embuilder.bat b/embuilder.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/embuilder.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emcmake b/emcmake
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emcmake
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emcmake.bat b/emcmake.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emcmake.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emconfigure b/emconfigure
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emconfigure
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emconfigure.bat b/emconfigure.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emconfigure.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emdwp b/emdwp
deleted file mode 100755
index 2f93cfaded2e4..0000000000000
--- a/emdwp
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$(dirname $0)/tools/emdwp.py" "$@"
diff --git a/emdwp.bat b/emdwp.bat
deleted file mode 100644
index 037c618638cdc..0000000000000
--- a/emdwp.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (tools\emdwp.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to tools\emdwp.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%tools\emdwp.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%tools\emdwp.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%tools\emdwp.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%tools\emdwp.py" %*
diff --git a/emmake b/emmake
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emmake
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emmake.bat b/emmake.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emmake.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emnm b/emnm
deleted file mode 100755
index 19fba1368d2b4..0000000000000
--- a/emnm
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$(dirname $0)/tools/emnm.py" "$@"
diff --git a/emnm.bat b/emnm.bat
deleted file mode 100644
index beacf497a4034..0000000000000
--- a/emnm.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (tools\emnm.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to tools\emnm.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%tools\emnm.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%tools\emnm.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%tools\emnm.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%tools\emnm.py" %*
diff --git a/emprofile b/emprofile
deleted file mode 100755
index 7a35f7a83c39d..0000000000000
--- a/emprofile
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$(dirname $0)/tools/emprofile.py" "$@"
diff --git a/emprofile.bat b/emprofile.bat
deleted file mode 100644
index 4f50f8249ee48..0000000000000
--- a/emprofile.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (tools\emprofile.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to tools\emprofile.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%tools\emprofile.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%tools\emprofile.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%tools\emprofile.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%tools\emprofile.py" %*
diff --git a/emranlib b/emranlib
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emranlib
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emranlib.bat b/emranlib.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emranlib.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emrun b/emrun
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emrun
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emrun.bat b/emrun.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emrun.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emscan-deps b/emscan-deps
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emscan-deps
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emscan-deps.bat b/emscan-deps.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emscan-deps.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emscons b/emscons
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emscons
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emscons.bat b/emscons.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emscons.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emsize b/emsize
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emsize
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emsize.bat b/emsize.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emsize.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emstrip b/emstrip
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emstrip
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emstrip.bat b/emstrip.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emstrip.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/emsymbolizer b/emsymbolizer
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/emsymbolizer
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/emsymbolizer.bat b/emsymbolizer.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/emsymbolizer.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/test/runner b/test/runner
index eef0f00c6730f..16710c6c5cf88 100755
--- a/test/runner
+++ b/test/runner
@@ -11,8 +11,8 @@
 # To make modifications to this file, edit `tools/run_python.sh` and then run
 # `tools/maint/create_entry_points.py`
 
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
+# $PYTHON -E does not ignore _PYTHON_SYSCONFIGDATA_NAME, an internal of cpython
+# used in cross compilation via setup.py, so we unset it explicitly here.
 unset _PYTHON_SYSCONFIGDATA_NAME
 
 if [ -z "$PYTHON" ]; then
diff --git a/tools/file_packager b/tools/file_packager
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/tools/file_packager
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/tools/file_packager.bat b/tools/file_packager.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/tools/file_packager.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
diff --git a/tools/maint/run_python.sh b/tools/maint/run_python.sh
index eef0f00c6730f..16710c6c5cf88 100755
--- a/tools/maint/run_python.sh
+++ b/tools/maint/run_python.sh
@@ -11,8 +11,8 @@
 # To make modifications to this file, edit `tools/run_python.sh` and then run
 # `tools/maint/create_entry_points.py`
 
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
+# $PYTHON -E does not ignore _PYTHON_SYSCONFIGDATA_NAME, an internal of cpython
+# used in cross compilation via setup.py, so we unset it explicitly here.
 unset _PYTHON_SYSCONFIGDATA_NAME
 
 if [ -z "$PYTHON" ]; then
diff --git a/tools/webidl_binder b/tools/webidl_binder
deleted file mode 100755
index eef0f00c6730f..0000000000000
--- a/tools/webidl_binder
+++ /dev/null
@@ -1,35 +0,0 @@
-#!/bin/sh
-# Copyright 2020 The Emscripten Authors.  All rights reserved.
-# Emscripten is available under two separate licenses, the MIT license and the
-# University of Illinois/NCSA Open Source License.  Both these licenses can be
-# found in the LICENSE file.
-#
-# Entry point for running python scripts on UNIX systems.
-#
-# Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-#
-# To make modifications to this file, edit `tools/run_python.sh` and then run
-# `tools/maint/create_entry_points.py`
-
-# $PYTHON -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-# of cpython used in cross compilation via setup.py.
-unset _PYTHON_SYSCONFIGDATA_NAME
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$EMSDK_PYTHON
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python3 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  PYTHON=$(command -v python 2> /dev/null)
-fi
-
-if [ -z "$PYTHON" ]; then
-  echo 'unable to find python in $PATH'
-  exit 1
-fi
-
-exec "$PYTHON" -E "$0.py" "$@"
diff --git a/tools/webidl_binder.bat b/tools/webidl_binder.bat
deleted file mode 100644
index e8840745a6d33..0000000000000
--- a/tools/webidl_binder.bat
+++ /dev/null
@@ -1,86 +0,0 @@
-:: Entry point for running python scripts on windows systems.
-::
-:: Automatically generated by `create_entry_points.py`; DO NOT EDIT.
-::
-:: To make modifications to this file, edit `tools/run_python.bat` and then run
-:: `tools/maint/create_entry_points.py`
-
-:: N.b. In Windows .bat scripts, the ':' character cannot appear inside any if () blocks,
-:: or there will be a parsing error.
-
-:: All env. vars specified in this file are to be local only to this script.
-@setlocal
-:: -E will not ignore _PYTHON_SYSCONFIGDATA_NAME an internal
-:: of cpython used in cross compilation via setup.py.
-@set _PYTHON_SYSCONFIGDATA_NAME=
-@set EM_PY=%EMSDK_PYTHON%
-@if "%EM_PY%"=="" (
-  set EM_PY=python
-)
-
-:: Work around Windows bug https://github.com/microsoft/terminal/issues/15212 : If this
-:: script is invoked via enclosing the invocation in quotes via PATH lookup, then %~f0 and
-:: %~dp0 expansions will not work.
-:: So first try if %~dp0 might work, and if not, manually look up this script from PATH.
-@if exist "%~f0" (
-  set "MYDIR=%~dp0"
-  goto FOUND_MYDIR
-)
-@for %%I in (%~n0.bat) do (
-  @if exist %%~$PATH:I (
-    set MYDIR=%%~dp$PATH:I
-  ) else (
-    echo Fatal Error! Due to a Windows bug, we are unable to locate the path to %~n0.bat.
-    echo To help this issue, try removing unnecessary quotes in the invocation of emcc,
-    echo or add Emscripten directory to PATH.
-    echo See github.com/microsoft/terminal/issues/15212 and
-    echo github.com/emscripten-core/emscripten/issues/19207 for more details.
-  )
-)
-:FOUND_MYDIR
-
-:: Python Windows bug https://bugs.python.org/issue34780: If this script was invoked via a
-:: shared stdin handle from the parent process, and that parent process stdin handle is in
-:: a certain state, running python.exe might hang here. To work around this, if
-:: EM_WORKAROUND_PYTHON_BUG_34780 is defined, invoke python with '< NUL' stdin to avoid
-:: sharing the parent's stdin handle to it, avoiding the hang.
-
-:: On Windows 7, the compiler batch scripts are observed to exit with a non-zero errorlevel,
-:: even when the python executable above did succeed and quit with errorlevel 0 above.
-:: On Windows 8 and newer, this issue has not been observed. It is possible that this
-:: issue is related to the above python bug, but this has not been conclusively confirmed,
-:: so using a separate env. var EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG to enable the known
-:: workaround this issue, which is to explicitly quit the calling process with the previous
-:: errorlevel from the above command.
-
-:: Also must use goto to jump to the command dispatch, since we cannot invoke emcc from
-:: inside a if() block, because if a cmdline param would contain a char '(' or ')', that
-:: would throw off the parsing of the cmdline arg.
-@if "%EM_WORKAROUND_PYTHON_BUG_34780%"=="" (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto NORMAL
-  ) else (
-    goto NORMAL_EXIT
-  )
-) else (
-  @if "%EM_WORKAROUND_WIN7_BAD_ERRORLEVEL_BUG%"=="" (
-    goto MUTE_STDIN
-  ) else (
-    goto MUTE_STDIN_EXIT
-  )
-)
-
-:NORMAL_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*
-@exit %ERRORLEVEL%
-
-:MUTE_STDIN
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit /b %ERRORLEVEL%
-
-:MUTE_STDIN_EXIT
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %* < NUL
-@exit %ERRORLEVEL%
-
-:NORMAL
-@"%EM_PY%" -E "%MYDIR%%~n0.py" %*