mirror of
https://gitflic.ru/project/openide/openide.git
synced 2025-12-16 22:51:17 +07:00
To activate conda on **nix, we provide a path to `active` script and a path to the env directory. Terminal shell integration scripts then "source" `activate` providing an env path as an argument. The latter is called `JEDITERM_SOURCE` env var, the former is `JEDITERM_SOURCE_ARGS`. The problem is those integration scripts treat `JEDITERM_SOURCE_ARGS` as a list, so they use shell magic to break it into several arguments, so `/path/foo bar/` effectively presented as `['/path/foo', 'bar/']`. To fix it, we introduce the ` JEDITERM_SOURCE_SINGLE_ARG ` key which means "do not explode argument." (cherry picked from commit a0a7c7a7bc8789078dd6cf109f4fd4386c9b7da6) IJ-MR-159065 PY-78762: Activate conda in Powershell. We used to use `Invoke-Expression` but then migrated to `&`. However, a conda activation script is a command (code block), not a file, so we need to use `Invoke-Expression` as '&' doesn't support it. We check if a file exists, and if it does -- we use '&' which is safe and fast. We use `Invoke-Expression` otherwise. Merge-request: IJ-MR-158505 Merged-by: Ilya Kazakevich <ilya.kazakevich@jetbrains.com> PY-78762 (partially): Conda activation for PS cleanup: 1. Use a conda path from SDK 2. report error using echo Merge-request: IJ-MR-160629 Merged-by: Ilya Kazakevich <ilya.kazakevich@jetbrains.com> GitOrigin-RevId: b16bd0b1babb1ea3b685daa5697426418356d089