be activate looks at the parent process of python.exe to determine which shell you are currently using. Typically, the parent is cmd.exe, or bash.exe.
But, because pip install generates a new executable for be, called be.exe, which in turn launches python.exe, then be.exe is deemed the parent process. That's why we're seeing this message.
The reason I haven't seen it on my development machine is because I'm running python -m be directly, which bypasses the pip generated exe.
A bug in the
pip installlogic.beactivate looks at the parent process ofpython.exeto determine which shell you are currently using. Typically, the parent iscmd.exe, orbash.exe.But, because pip install generates a new executable for be, called
be.exe, which in turn launchespython.exe, thenbe.exeis deemed the parent process. That's why we're seeing this message.The reason I haven't seen it on my development machine is because I'm running
python -m bedirectly, which bypasses thepipgeneratedexe.