7309a62c8c
We can avoid specifying versions here, but ... 1. It won't be possible to run tests locally without checking what versions are supported (going to TeamCity config) 2. It won't be possible to specify dependencies for each Python version separately when it is required (not yet, but will be soon) Hardcoding Python versions in two places for `pydevd` tests looks ugly, but at the moment I have no better ideas. Will investigate as a separate task in PCQA-447 (cherry picked from commit cc9e50cd7a742b8265497cdc56a49a6be0db38a8) IJ-MR-138586 GitOrigin-RevId: 717d434d6fd72a6cb6ac0a361917ad22e8e62687
PyCharm Community Edition
The "python" directory in the source repository contains the source code of PyCharm Community Edition and the Python plugin for IntelliJ IDEA Community Edition.
Building and Running
The code is part of the main IntelliJ IDEA Community Edition project and is compiled together with the rest of the codebase. To run PyCharm Community Edition, please use the provided run configuration "PyCharm Community Edition". To run IntelliJ IDEA with the Python plugin, please use the "IDEA with Python plugin" run configuration.
To run the test suite, use the built-in JUnit test runner and run all tests in the "python-community-tests" module.
Building from the Command Line
To build the distribution archive of PyCharm Community Edition, execute build.xml Ant build script in this directory. The results of the build execution can be found at out/artifacts.
Building the Python Plugin
To build the Python plugin for IntelliJ IDEA Community Edition:
-
Download the .tar.gz distribution of the most recent EAP or release build of IntelliJ IDEA Community Edition;
-
Run the following command:
ant -Didea.path= -Didea.build.number=<build number of the build you're using> plugin
The .zip file of the built plugin will be placed at distCE/python-community-.SNAPSHOT.zip