Pycharm doesn't activate Anaconda virtual environment - on Windows 7 Follow

I'm using Pycharm Pro 2017.3 EAP (PY-173.34153.3) on Windows 7 Pro, 64-Bit.

The root Anaconda environment is Python 2.7, but I have several Python 3.6 environments created.

For my PyCharm project, I've selected the 3.6 interpreter, and PyCharm shows this its terminal window.

(C:\ProgramData\Anaconda2\envs\py36dev) C:\Users\MyUserName\Documents\Sources\GIT\Python\MyProject>

Python 3.6 is invoked when I run my application in the terminal as well as through the debugger. This is what is expected.

However, the Anaconda virtual environment for Python 3.6 is not really activated.

conda list shows the packages for the root Anaconda environment, which is Python 2.7

(C:\ProgramData\Anaconda2\envs\py36dev) C:\Users\MyUserName\Documents\Sources\GIT\Python\MyProject>conda list
# packages in environment at C:\ProgramData\Anaconda2:
#
_license 1.1 py27_1
alabaster 0.7.10 py27_0
anaconda custom py27_0
anaconda-client 1.6.3 py27_0
anaconda-navigator 1.6.2 py27_0
anaconda-project 0.6.0 py27_0
asn1crypto 0.22.0 py27_0
astroid 1.4.9 py27_0

When I fully activate the 3.6 environment in the Pycharm terminal:

activate py36dev

the prompt changes as expected, indicating that the desired Anaconda environment is fully activated.

(py36dev) (C:\ProgramData\Anaconda2\envs\py36dev) C:\Users\MyUserName\Documents\Sources\GIT\Python\MyProject>

conda list now shows the packages for the active environment, as expected.

conda list
# packages in environment at C:\ProgramData\Anaconda2\envs\py36dev:
#
_license 1.1 py36_1
alabaster 0.7.10 py36_0
anaconda 4.4.0 np112py36_0
anaconda-client 1.6.3 py36_0

It looks like PyCharm isn't really activating the Anaconda environment, even though it is using the correct interpreter that I've selected.

It seems as though this could cause a world of problems.