Using virtualenv with --python and a 32 bit Python breaks on Windows

[The-Compiler]

When trying to use virtualenv started with a 64bit python and passing --python=/path/to/32bit/python, this breaks on Windows:

C:\Users\florian\tmp>C:\Python34\python.exe -m virtualenv --python=C:\Python34_x32\python.exe venv3
Running virtualenv with interpreter C:\Python34_x32\python.exe
Fatal Python error: Failed to initialize Windows random API (CryptoGen)

I investigated a bit and it seems this happens when using subprocess with env=... to start python in general - I opened Issue 24493 in Python's tracker because of that.

However I think virtualenv should work around this issue if possible. What do you think about not using env= and not setting VIRTUALENV_INTERPRETER_RUNNING, and instead adding a hidden argument which is passed when re-executing?

I also thought about removing the --python argument from the commandline, but that seems brittle, as e.g. --python=... or --python ... or -p ... could be passed.

If that sounds like an acceptable workaround, I can open a PR with the change.

[Ivoz]

@The-Compiler would appreciate if you could check if the above commit solves the issue

https://github.com/Ivoz/virtualenv/archive/early-syspath-removal.zip

[The-Compiler]

It doesn't, unfortunately.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Just add a comment if you want to keep it open. Thank you for your contributions.