# PEP 773: A Python Installation Manager for Windows **URL:** \ **Category:** PEPs\ **Created:** [January 21, 2025, 11:58pm UTC](https://discuss.python.org/t/pep-773-a-python-installation-manager-for-windows/77900 "2025-01-21T23:58:55Z")\ **Posts on this page:** 1\ **Showing post:** 223
**Author:** ![Andrej730](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/andrej730/32/19993_2.png) [@Andrej730](https://discuss.python.org/u/Andrej730)\ **Post date:** [November 22, 2025, 5:26pm UTC](https://discuss.python.org/t/pep-773-a-python-installation-manager-for-windows/77900/223 "2025-11-22T17:26:01Z")
Are there plans to include debug binaries (`pythond`, `python311_d.dll`) to `PythonTest` or to some separate tag? I guess it’s the last advantage that classic installer has for me. I’ve switched to PIM for all system Pythons I need occasionally, but I still use the classic installer for the main Python I use, since it provides debug binaries that I need to build and run some extensions in Debug configuration. Btw, though `--download` advertised in the docs mainly as the tool to perform offline installations, I’ve found that it works really well for downloading Python just to build something, without creating any system footprint. I previously used `nuget` for this purpose, but now `nuget` seems inferior since it doesn’t have a package that has debug symbols, while `PythonTest` PIM tag does, though only for Python 3.11+. --- _[View the full topic](https://discuss.python.org/t/pep-773-a-python-installation-manager-for-windows/77900)._