| Git Clone URL: | https://aur.archlinux.org/pycharm.git (read-only, click to copy) |
|---|---|
| Package Base: | pycharm |
| Description: | The only Python IDE you need. Bundled with the official JetBrains Runtime (JBR) |
| Upstream URL: | https://www.jetbrains.com/pycharm/ |
| Licenses: | custom |
| Conflicts: | pycharm-community-edition, pycharm-professional |
| Provides: | pycharm |
| Replaces: | pycharm-professional |
| Submitter: | Xavier |
| Maintainer: | Zpecter (Meaulnes) |
| Last Packager: | Zpecter |
| Votes: | 308 |
| Popularity: | 1.38 |
| First Submitted: | 2025-10-04 18:47 (UTC) |
| Last Updated: | 2026-05-15 20:18 (UTC) |
I just also encountered a speed-up build error
File "/tmp/pycharm-professional/src/pycharm-2024.3.2/./plugins/python-ce/helpers/pydev/setup_cython.py", line 111, in build_extension
from Cython.Build import cythonize
ModuleNotFoundError: No module named 'Cython'
took me a while to figure out that I still had the legacy cython0 installed. Using the normal cython instead solved the issue for me. (Thought I'd share this and save somebody else the debugging time.)
@hornobster, yes the error could be because your PYenv, try to download the source with yay -G and build it manually makepkg in a clean shell. If the problem persists, delete the section prepare() and build() in the pkgbuild file
I can't make it work. I have reinstalled again in a clean shell with yay pycharm-professional --overwrite '/opt/pycharm-professional/plugins/python-ce/helpers/pydev/*', but nothing changed.
Could it be related to my use of pyenv? PYenv isn't active when installing pycharm, but I use it for my projects (e.g. for python 3.12 venv) and when trying to debug.
Hi @hornobster, it seems like you have some issues with the Cython Speed Up, try to build the package in a clean shell (or clean chroot) maybe you have some rust, python or other configuration in your environment. When you are building the package check the logs for errors.
I am getting the following error when trying to debug any python script:
Traceback (most recent call last):
File "/opt/pycharm-professional/plugins/python-ce/helpers/pydev/pydevd.py", line 59, in <module>
from _pydevd_bundle.pydevd_trace_dispatch import (
ImportError: cannot import name 'trace_dispatch' from '_pydevd_bundle.pydevd_trace_dispatch' (/opt/pycharm-professional/plugins/python-ce/helpers/pydev/_pydevd_bundle/pydevd_trace_dispatch.py)
I have tried [aur helper] pycharm-professional --overwrite '/opt/pycharm-professional/plugins/python-ce/helpers/pydev/*', but it didn't work.
Disabling the cython optimisations debugging works.
@0xc0ffee, I decided to change it because it was not only due to what you mentioned; other people also reported some problems with the post-script build. Originally, I included it in the post-script for reasons related to what you mentioned (specifically regarding the paths, which is why you can see a warning during the pkgbuild process). However, I believe this is not an issue, and they work well. These are binaries, and they are linked more to the Python/Cython versions than to the paths, unless someone reports or detects an issue related to this.
@Xavier Thanks for the update.
Maybe I didn't express my idea clearly, but my point is that I'm pretty sure the error message that supply730 and I saw is a false alarm and it is benign. If you don't use pamac as your frontend for libalpm, you will not encounter that false alarm. I think the ideal fix here would be to submit a PR to Manjaro's pamac with better error detection logic.
JetBrains supplies pre-built Cython modules only for macOS and Windows, not for Linux. I am against the idea of lifting the Cython speedups job to packaging time. I know that in many cases the machine building this AUR package will also be the machine using it, but do we really want to make such an assumption? If there is any Python environment discrepancy between the packaging machine and the using machine, I'm worried those Cython modules may not work reliably. I believe this is one of the reasons why JetBrains wants Linux users to build those modules themselves.
MANUAL INTERVENTION FOR v2024.3.1.1:
Due to the latest changes for the cython speed up, this release is going to show a commit transaction conflicting files, to fix this you need to enable Cython Speed Up file overwriting:
[aur helper] pycharm-professional --overwrite '/opt/pycharm-professional/plugins/python-ce/helpers/pydev/*'
or after manual build:
sudo pacman -U pycharm-professional-2024.3.1.1-1-x86_64.pkg.tar.zst --overwrite '/opt/pycharm-professional/plugins/python-ce/helpers/pydev/*'
@0xc0ffee I prefer to compile the Cython speed up for the package rather than letting the user download it, but it is good to know that exist that option, thanks!. Due to some post-installation issues I moved the cython speed up into the PKGBUILD.
@Poscat @MikeBreytenbach for the next release I'm going to check that option, thanks.
Pinned Comments
Meaulnes commented on 2026-03-27 16:37 (UTC)
This comment from @AvacadoCookie should be pinned, IMO.
If anyone is getting errors about
Cythonorsetuptools, and they are usingConda, that comment has the answer.If anyone is getting errors about
Cythonorsetuptools, and they are usingpyenv, there are 2 possible ways to fix it:pyenv local systemto set Python back to the system installed Python for this session.pip install Cython setuptoolsto install the necessary packages to your preferred python installation.AvocadoCookie commented on 2025-12-14 16:22 (UTC)
For all users with
ModuleNotFoundError: No module named 'Cython'or'setuptools'reported, please try the following methods to address the problem:condaenvironment. Now afterwhich pythontyped in console, the output should be/usr/bin/python.pacman -S cython python-setuptools.