The non-impl modules for these plugins now contain more or less just their plugin.xml files
that declare corresponding dependencies.
GitOrigin-RevId: 84fc4761a595912d676cff1e2ab58fba03a8cd22
Module intellij.python.configure used to be included into both PyCharm Customization and Python plugins leading to
duplicate classes in these plugins. Even after removing it from intellij.pycharm.community.customization it was
unclear what should go into intellij.python.configure, since its *.xml was used only in
intellij.pycharm.community.customization while its source code was used either in PyCharm Customization or in
intellij.python.community.impl + PyCharm Customization.
GitOrigin-RevId: 008601cd993cebd22bbfe69f963e53a690691608
During the recent refactoring a Python plugin only file python-community-plugin-core.xml got included
into the Python plugin which is now bundled with PyCharm. It resulted in using Python plugin specific
components that were designed for the UI of IntelliJ, not PyCharm. This change restores the
registration of PyIdeCommonOptionsFormFactory and moves all includes of python-community-plugin-core.xml
to Python plugin specific files.
GitOrigin-RevId: cd8b6d9b68266ca99f206c005ba73a2e77657950
Python plugin stored the interpreter setting as a module sdk, which was wiped out with it's order entries by Clion.
The fix is to store the interpreter setting in a facet and reinitialize it after Clion model clearing.
