unable to get ide-terminal to operate within virtual environment

[mghah]

• [x] I have reset Atom to defaults prior to submitting report.
• [ ] I have not reset Atom to defaults prior to submitting report.

  Description

  i want to use this atom terminal in a virtual environment but it does not work. i create a virtual environment using conda, activate it, launch atom from it, but the terminal from ide-terminal package still belongs to (base). Furthermore, even when i activate virtual environment from IDE-terminal in atom, it is still stock in base environment. i.e., even though it seems like it has switched to the virtual environment, it still points to base environment and fetches python version and installed packages as if its is still in base env.

Steps to reproduce

1. install atom
2. install ide-terminal
3. create a virtual env with conda (outside of atom)
4. activate the virtual environment
5. launch atom from the activated virtual environment terminal
6. open an ide-terminal in atom
7. observe that it is still pointing to base and not the virtual environment as expected

Expected behavior: terminal in atom should belong to virtual environment as atom is launched from a virtual env

Actual behavior: terminal in atom defaults to base env even though atom was launched from a virtual env. also after manually changing the env in ide-terminal it still used base env setup.

Reproduces how often: 100%

Versions

> atom --version
1.4.2.0

> apm --version

OS name and version: macOS Sierra 10.12 Platformio-ide-terminal version:2.10

Additional Information

[jameswilliams1]

bump - I've had to uninstall as I noticed when platformio is present it uses the normal system path rather than from whatever terminal its called from. Checked in process.env["PATH"] with and without platformio installed, without is as expected, with uses system default $PATH.

OS: Distributor ID: Debian Description: Debian GNU/Linux bullseye/sid Release: testing Codename: bullseye

Atom: Atom : 1.43.0 Electron: 4.2.7 Chrome : 69.0.3497.128 Node : 10.11.0 platformio: 2.10.0

[mjsielerjr]

Same problem. System info • MacOS Catalina: 10.15.4 • Atom: 1.45.0

[lozferatu]

SOLVED

I had the same ( frustrating problem), luckily I think one of the helper packages I had gave a more useful error.

It's down to the Execution Policy - basically default is to not let power shell run more than single line commands ( so not scripts).

In terminal type: Set ExecutionPolicy -Scope CurrentUser

Then when prompted ExecutionPolicy:Unrestricted