``PYCHARM_HOSTED`` makes ``Coloroma`` assume that ``isatty() == true`` (even for bat file redirected to another file) which leads to problems on Windows. See issue comments for more info
GitOrigin-RevId: b82b25e7175330ae86604fc14012ef85e2b8ba0b
Each sdk has additional data with flavor and flavor-specific data. For target-based SDK there is also target information. ``PySdkExt`` has extension method that uses this data to execute code on some SDK. For Conda we store path to conda binary and env name.
GitOrigin-RevId: c63b57aac9b5a267b3a6710902670bfe7d10c722
The problem is ``sys.stdout.encoding``.
On Unix Python uses ``LC_`` which is UTF-8 since late 2000s.
But on Windows for non-console based executions (with stdout redirected) it uses one byte encoding (aka non-unicode programs charset) due to backward compatibility with 9x/me.
With one-byte charset you can't have both latin-1 and cyrillic characters.
To fix that, we provide ``PYTHONIOENCODING`` which sets charset explicitly
GitOrigin-RevId: 5c3304e002d80fb5780f11f05fe5f4d1b6aef3ad
``homePath`` isn't unique for things like conda and remote interpreter.
Merge-request: IJ-MR-95540
Merged-by: Ilya Kazakevich <ilya.kazakevich@jetbrains.com>
GitOrigin-RevId: 2695cd29f2e102e48e22d751d8fb37a5aea567e4
If "python.use.targets.api" registry flag is disabled:
- display target-based interpreters as invalid;
- show an error on an attempts to run or debug Python run configuration with an assigned target-based Python interpreter;
- show an error on trying to open Python console with a target-based Python interpreter;
- show a warning on an attempt to generate skeletons for target-based interpreters;
- show an empty list of packages for target-based Python interpreters.
GitOrigin-RevId: 97ee828ab289e5104f0539c9ab49e6fab99fe56b
DS-1661 New opened terminal sessions use the Workspace environment even though the opened folder has a different environment set in settings
GitOrigin-RevId: 286d7d076429f6b429b8b5378229d1336a6bca06
DS-1661 New opened terminal sessions use the Workspace environment even though the opened folder has a different environment set in settings
GitOrigin-RevId: e47df9bc9b6ee65e85f0667f0390be7edce4a891
- fix absence of package name if installation failed via file-level warning on requirements file
- get rid of unnecessary columns
- make the dialog resizable
- add forgotten dot to the troubleshooting tip#1
- add paddings to output and command text areas
- move hardcoded strings to bundles
IJ-CR-16145
GitOrigin-RevId: 6bafccd46dc6eb01db31d33d8979cca9c2b99c20
It causes some weird problems with escaping, when in some places the platform
escapes `C:\foo bar\` as `"C:\foo bar\\"` and as `"C:\foo bar"\` in others
(compare ParametersListUtil.escape and CommandLineUtil.backslashEscapeQuotes).
One way or another, Python interpreter gets the path to the skeletons directory
as two separate command line arguments. The platform escaping problem needs
further investigation, but removing the trailing backslashes is the simplest
workaround on the Python plugin side. We stripped them in generator3 anyway.
GitOrigin-RevId: 52c0c1d3733cc004c1f0c2f1bf8cc186dfa698de
PyTransferredSdkRootsKt#transferRoots and PyTransferredSdkRootsKt#removeTransferredRoots skip sdks that are not equal to module one (editable as well).
That's why roots changes were not applied in PythonSdkUpdater#updateSdkPaths but paths to transfer were successfully set.
When PythonSdkUpdater#updateSdkPaths was executed for original sdk, roots changes were not applied since there were no changes in paths to transfer (they were shared with editable copy).
Update PythonSdkAdditionalData containers usages: they returned cached values in `getPathsAsVirtualFiles` after `killAll` was called.
IJ-CR-10935
GitOrigin-RevId: 72a99f7b14e4d30c5886accb0db56d463890f265
It speeds up virtual environment creation (PY-41172), although from now on the latest releases of packaging tools will be installed in the created virtual environment after the 28 days period that should guarantee we are not pulling in automatically releases that have known bugs within (https://virtualenv.pypa.io/en/latest/user_guide.html#wheels)
IJ-CR-9549
GitOrigin-RevId: 563409e9f7ef1d61572989555f572b06b19ded85
DS-1519 Make "Launch DataSpell" button disabled and provide corresponding messages when no valid environment configuration selected on environment tab
GitOrigin-RevId: 6ccde477ddd0beea348cdc364cf2d89857094eaf
DS-1519 Make "Launch DataSpell" button disabled and provide corresponding messages when no valid environment configuration selected on environment tab
GitOrigin-RevId: 6027f6034533ca5716c3d5bcc4f599d75efa8f4a
No need to have two methods and break nullable safety.
Poetry plugin could be broken by this change, but Semyon.Proshev will send them a patch)
GitOrigin-RevId: 024cd4861ff1cb65e34e5c2e6c5032ad86205b60
