When debugging or testing improvements to the python build system (python.mk) in Maneage, it would be good to have a clean method for uninstalling all python libraries and binaries and python module libraries and binaries.

My best recent attempt was

rm -fv .local/version-info/python/; rm -fv .local/bin/python; rm -fr .local/lib/python*; rm -fr .build/.cache/Python-Eggs/; rm -fv .local/version-info/proglib/python-3.10.6; rm -fv .local/bin/cy*; rm -fv .local/version-info/proglib/cy*; rm -fvr .local/include/python3.10* ; rm -fv .local/bin/f2py*

but on doing './project configure --existing-conf' I still got fatal errors of the style

FileExistsError: File already exists: ...

The only practical method I found of uninstalling python, in order to get a clean test of an update to python, was to remove the whole '.build/' tree.  (In principle, removing '.build/software/' should be enough.)

(In Debian, aptitude purge PACKAGE removes all traces of the package, including any configure files installed with PACKAGE and subsequently modified by the sysadmin. An alternative is aptitude remove PACKAGE , which does not remove configuration files.)