| 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: | 309 |
| Popularity: | 2.35 |
| First Submitted: | 2025-10-04 18:47 (UTC) |
| Last Updated: | 2026-05-15 20:18 (UTC) |
@XavierCLL Please don't do what @klaasjanelzinga suggests. Not only it's wrong place to set the XZ_OPT env.var., it also doesn't have any effect on the package build speed, because XZ is not involved since January 2020.
@klaasjanelzinga If you build packages just for yourself, you can omit package compression simply by changing the line PKGEXT='.pkg.tar.zst' (or maybe .pkg.tar.xz still in your case) to PKGEXT='.pkg.tar'.
good catch @alorence, fixed in the new release, thanks
I recently encountered issues to build Cython extension for a project using python 3.6, installed using pyenv, while my system use python3.9 by default.
The error was easily reproducible in console, and was related to missing _pydevd_frame_eval/pydevd_frame_evaluator.c in pydevd folder.
I noticed that the PKGBUILD run
find pycharm-${pkgver}/plugins/python/helpers/pydev/ \( -name *.c -o -name *.so -o -name *.pyd \) -delete
as first command in the build step. While I understand that *.so and *.pyd files may be deleted before building, I don't understand why *.c files are deleted too. Is it an error ?
By the way I edited the PKGBUILD before building the package to remove *.c files deletion, and I was able to build Cython extension for my py3.6 project
find pycharm-${pkgver}/plugins/python/helpers/pydev/ \( -name *.so -o -name *.pyd \) -delete
I also had the problem "ModuleNotFoundError: No module named 'Cython'" when building from the terminal with Pamac on Manjaro. However, I had a conda virtual environment activated.
The build finished successfully for me when using Pamac GUI.
I don't have errors in the build but I'll check it, thanks @Cthulu201
I usually build in a clean chroot (no makepkg -s) and was getting Cython errors. I've modified your PKGBUILD so it builds and runs for me. Happy for any feedback: https://0bin.net/paste/0tfmKwCN#wGHqvnUJ7bAHshbTKahSR1DeqMyWndoN+CPmEaHz9KX
It looks like my issues was that I use pyenv and I had 3.9 set as the global python version. setting pyenv global system works for me.
Note that there is an issue with setting the global version to system on Arch, in that it check for python being in a bin dir, not sbin and on my system /usr/sbin was a symlink to /usr/bin and sbin was first. To fix it I unlinked /usr/sbin, set pyenf global to system, installed pycharm, then added the link back.
I am getting the same error. Fresh terminal with no environment loaded, and nothing in PYTHONPATH. I also made sure to clear the cache and do a clean build.
==> Starting build()...
Traceback (most recent call last):
File "/home/shawn/.cache/yay/pycharm-professional/src/pycharm-2021.1/plugins/python/helpers/pydev/setup_cython.py", line 112, in <module>
build_extension("_pydevd_bundle", extension_name, target_pydevd_name, force_cython, extension_folder, True)
File "/home/shawn/.cache/yay/pycharm-professional/src/pycharm-2021.1/plugins/python/helpers/pydev/setup_cython.py", line 69, in build_extension
from Cython.Build import cythonize # @UnusedImport
ModuleNotFoundError: No module named 'Cython'
==> ERROR: A failure occurred in build().
Aborting...
error making: pycharm-professional
Works now, I did indeed have a virtualenv active. Oops and thanks @XavierCLL, @klaasjanelzinga!
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.