When Python is installed in a path containing spaces (e.g., C:\Program Files\Python39) on Windows, and a file named C:\Program exists on the filesystem, virtualenv's pydoc command fails with the error:

Unable to create process using 'c:\program files\python39\python.exe'
This happens because Windows command interpreter splits unquoted paths at spaces, interpreting C:\Program Files\Python39\python.exe as two separate arguments:

C:\Program (which exists as a file)
Files\Python39\python.exe
When Windows tries to execute C:\Program as if it were an executable, the command fails.

The issue stems from unquoted Python executable paths in activation scripts.

Solution:
Quotes ensure Windows treats the entire path as a single argument, even with spaces, and the call operator in PowerShell properly handles commands with spaces in their paths.

Fixes: #2985

• ran the linter to address style issues (tox -e fix)
• wrote descriptive pull request text
• ensured there are test(s) validating the fix
• added news fragment in docs/changelog folder
• updated/extended the documentation