1. Delete `intellij.python.community.impl.xml` (move content to `PythonCore` plugin). It is necessary to fix incorrect dependencies: `PythonCore`, `Pythonid` include the same module.
2. Fixed dependencies: if some plugin/module needs Python core functionality, then it should depend on `PythonCore`.
Co-authored-by: Vladimir Koshelev <Vladimir.Koshelev@jetbrains.com>
Merge-request: IJ-MR-136158
Merged-by: Egor Eliseev <Egor.Eliseev@jetbrains.com>
GitOrigin-RevId: ce9ed4c17f601ee1ca2b6cf608f4e30fdac1d879
Layout:
JPS modules
`intellij.python.community`
`intellij.python.community.impl`
`intellij.python.parser`
`intellij.python.psi`
`intellij.python.psi.impl`
`intellij.python.ast`
use package `com.jetbrains.python`
and go to `intellij.python.community.impl` v2 module
JPS module
`intellij.python`
uses package `com.intellij.python.pro`
and goes to `intellij.python/pro` v2 module
Both v2 modules (along with lots of others) come with
`PythonId` (prof) or `PythonCore` (community) plugins
DS bundles `intellij.python.community.impl`
Idea and other Mini IDEs get `PythonCore` or `PythonId` plugin that bundle modules for Idea and mini IDEs
GitOrigin-RevId: 98f418c52d90d51b9adf3250c561f2c36c767e2d
Since we don't store conda path in SDK, we only can ask user to run `conda init powershell` to patch her profile and add ``conda.exe`` to ``PATH``.
After that, we can run ``conda activate``.
GitOrigin-RevId: c6cdac9252f022d7bcd1e020c8aaeffaa89b3fbf
They don't make any sense since
- they are not required for bundled plugins (com.intellij.ide.plugins.IdeaPluginDescriptorImpl#myVersion will be filled with IDE version)
- they will be overwritten during the build for pluginsToPublish (org.jetbrains.intellij.build.impl.DistributionJARsBuilder#setPluginVersionAndSince)
Still they may affect plugins loading mechanism, e.g. see https://youtrack.jetbrains.com/issue/GO-6741 or https://youtrack.jetbrains.com/issue/IDEA-188964
