Package Details: pycharm 2026.1.4-1

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: 1.14
First Submitted: 2025-10-04 18:47 (UTC)
Last Updated: 2026-07-03 19:20 (UTC)

Dependencies (19)

Required by (0)

Sources (4)

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 Cython or setuptools, and they are using Conda, that comment has the answer.

If anyone is getting errors about Cython or setuptools, and they are using pyenv, there are 2 possible ways to fix it:

  1. pyenv local system to set Python back to the system installed Python for this session.
  2. pip install Cython setuptools to 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:

  1. Quit conda environment. Now after which python typed in console, the output should be /usr/bin/python.
  2. Try again.
  3. If the installation still failed, try again after pacman -S cython python-setuptools.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 49 Next › Last »

Xavier commented on 2025-04-17 13:35 (UTC)

I'm agree with having a single package called "pycharm," but where? I just emailed the maintainers of "pycharm-community-edition" to see how best to proceed. While I wait for their response, I've just updated this with the current name. I'll keep you posted on any updates.

Ashark commented on 2025-04-17 08:33 (UTC)

@nonZero Yeah, I agree. Needs renaming to just "pycharm". The question is, will not this name wanted to be used by the official package "pycharm-community-edition" from [extra]?

nonZero commented on 2025-04-17 07:35 (UTC) (edited on 2025-04-17 07:36 (UTC) by nonZero)

As pycharm is moving to a "united" approach, eliminating "professional" and "community" distinction, maybe it is time to rename the package to "pycharm"? https://blog.jetbrains.com/pycharm/2025/04/unified-pycharm/

Xavier commented on 2025-03-29 01:44 (UTC)

@tilx, read these instructions on https://aur.archlinux.org/packages/pycharm-professional#comment-1002854 about manual intervention after update v2024.3.1.1

tilx commented on 2025-03-28 09:28 (UTC) (edited on 2025-03-28 09:31 (UTC) by tilx)

I got an error upgrading PyCharm:

error: failed to commit transaction (conflicting files)
pycharm-professional: /opt/pycharm-professional/plugins/python-ce/helpers/pydev/pydevd_attach_to_process/attach_linux_amd64.so exists in filesystem

Renaming the existing file let me complete the upgrade.

There is only a small difference between the binaries:

$ cmp -l /opt/pycharm-professional/plugins/python-ce/helpers/pydev/pydevd_attach_to_process/attach_linux_amd64.so{,.old}
  745 224 204
  746 267 214
  747 216 345
  748  66 312
  749 275 244
  750  31 316
  751 151 163
  752  51 342
  753 312  33
  754  16 266
  755 153  15
  756  77 355
  757 173 176
  758 366 326
  759 143 240
  760 132  76
  761 140  60
  762 176 273
  763   2 367
  764 253 333
24878  65  64
24880  62  71
24881  60  61
24882  67  60

hornobster commented on 2025-02-08 16:55 (UTC) (edited on 2025-02-08 17:45 (UTC) by hornobster)

@Xavier I still can't get it to work.

I have downloaded the package source with yay -G pycharm-professional, built the package with makepkg without touching the PKGBUILD first, and then retried after deleting both prepare() and build() from PKBUILD.

For now I am running all debug sessions with PYDEVD_USE_CYTHON=NO;PYDEVD_USE_FRAME_EVAL=NO as env variables.

EDIT: I think the problem is that the Cython extension is compiled for the system python, python 3.13, while I'm trying to debug a script in a venv for python 3.12. I don't know if there is a proper way of doing this.

EDIT 2: That was the problem. In PKGBUILD build() I have added a second extension compilation like so:

    # compile PyDev debugger used by PyCharm to speedup debugging
    python ./plugins/python-ce/helpers/pydev/setup_cython.py build_ext --inplace --force-cython
    /home/user/.pyenv/versions/3.12.8/bin/python ./plugins/python-ce/helpers/pydev/setup_cython.py build_ext --inplace --force-cython

I don't know if it would make sense to automatically build the extension for each installed pyenv python version in the PKGBUILD.

unbis commented on 2025-02-06 14:17 (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.)

Xavier commented on 2025-02-06 12:52 (UTC)

@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

hornobster commented on 2025-02-06 11:28 (UTC)

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.

Xavier commented on 2025-02-03 20:22 (UTC)

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.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 49 Next › Last »