Is anyone else seeing some odd behaviors with the custom python environments? I did a full uninstall and started over from scratch just in case.
Issue:
When trying to install a package from within ArcGIS Pro into a custom environment, the package appears to not install. If you do it via command (ie. python.exe -m pip install xyz), it works like a champ, but the software does not see the package as having been installed.
If using -m pip install on the command line, the package shows up, is accessible, etc. Typical behaviors one would expected there.
Expected behavior:
Python packages install as they did for 2.7.3 and the interface reflects the change.