Conda Environment Status Shows Full Path
See original GitHub issueProblem Description
@steff456 Environment status shows full path to conda environment, rather than just environment name. Pyenv environment status shows correctly.


Versions
- Spyder version: 4.2.0.dev0 0dfbe8967
- Python version: 3.7.9 64-bit
- Qt version: 5.9.6
- PyQt5 version: 5.9.2
- Operating System: Darwin 19.6.0
Dependencies
# Mandatory:
applaunchservices >=0.1.7 : 0.2.1 (OK)
atomicwrites >=1.2.0 : 1.4.0 (OK)
chardet >=2.0.0 : 3.0.4 (OK)
cloudpickle >=0.5.0 : 1.6.0 (OK)
diff_match_patch >=20181111 : 20200713 (OK)
intervaltree >=3.0.2 : 3.1.0 (OK)
IPython >=4.0 : 7.18.1 (OK)
jedi =0.17.2 : 0.17.2 (OK)
jsonschema >=3.2.0 : 3.2.0 (OK)
nbconvert >=4.0 : 6.0.7 (OK)
numpydoc >=0.6.0 : 1.1.0 (OK)
parso =0.7.0 : 0.7.0 (OK)
pexpect >=4.4.0 : 4.8.0 (OK)
pickleshare >=0.4 : 0.7.5 (OK)
psutil >=5.3 : 5.7.2 (OK)
pygments >=2.0 : 2.7.2 (OK)
pylint >=1.0 : 2.6.0 (OK)
pyls >=0.35.0;<1.0.0 : test-selector-01+92.g0dfbe8967 (OK)
pyls_black >=0.4.6 : 0.4.6 (OK)
pyls_spyder >=0.1.1 : 0.1.1 (OK)
qdarkstyle >=2.8 : 2.8.1 (OK)
qtawesome >=0.5.7 : 1.0.1 (OK)
qtconsole >=4.7.7 : 4.7.7 (OK)
qtpy >=1.5.0 : 1.9.0 (OK)
rtree >=0.8.3 : 0.9.4 (OK)
setuptools >=39.0.0 : 50.3.0.post20201006 (OK)
sphinx >=0.6.6 : 3.2.1 (OK)
spyder_kernels >=1.9.4;<1.10.0 : 1.10.0.dev0 (OK)
three_merge >=0.1.1 : 0.1.1 (OK)
watchdog >=0.10.3 : 0.10.3 (OK)
zmq >=17 : 19.0.2 (OK)
# Optional:
cython >=0.21 : 0.29.21 (OK)
matplotlib >=2.0.0 : 3.3.2 (OK)
numpy >=1.7 : 1.19.2 (OK)
pandas >=1.1.1 : 1.1.3 (OK)
scipy >=0.17.0 : 1.5.2 (OK)
sympy >=0.7.3 : 1.6.2 (OK)
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Activating conda environment with its full path - Stack Overflow
Navigate to the custom folder where you want to create the new environment. · D:\condaEnvs>conda create --prefix=FastAI --> This creates a conda ...
Read more >Managing environments - Conda
With conda, you can create, export, list, remove, and update environments that have different versions of Python and/or packages installed in them.
Read more >Manage your Python Virtual Environment with Conda
Conda can no longer find your environment by your environment name, you will have to specify the environment's full path to activate it...
Read more >Working with Environments – Introduction to Conda for (Data ...
A Conda environment is a directory that contains a specific collection of Conda packages that you have installed. For example, you may be...
Read more >PATH not set by conda activate · Issue #9392 - GitHub
Conda respects your PATH order and will not reorder anything upon activation/deactivation but instead finds the currently active environment and ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Okay, I found the problem. subprocess calls for conda were getting messed up by environment variables (probably PYTHONHOME) from the macOS application. All should be fixed with #14123
I still see the full path instead of the env name on Windows, though it may be a side effect of the fact that the new feature is not working at all, per #14160