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 10 11 12 .. 49 Next › Last »

iamkarlson commented on 2024-04-08 12:00 (UTC)

It's not only arch issue or even only wayland issue, but seems like all distros could be affected: https://youtrack.jetbrains.com/issue/PY-71746/As-of-yesterday-Pycharm-and-IntelliJ-crashes-and-kills-my-Ubuntu-22.04-session

There's a workaround to remove a config.

mv $HOME/.config/JetBrains/PyCharm2024.1/options/other.xml $HOME/.config/JetBrains/PyCharm2024.1/options/other.xml.bak            

iamkarlson commented on 2024-04-08 11:55 (UTC)

@lybin pycharm also doesn't start. I can report to sway but it's pycharm that is not working and not sway.

lybin commented on 2024-04-08 11:00 (UTC)

Congrats, report to sway, not here :)

iamkarlson commented on 2024-04-08 10:55 (UTC)

The latest version crashes sway:

 segfault at 40 ip 000077a6af765c38 sp 00007ffc4d64bd08 error 6 in libwayland-server.so.0.22.0[77a6af763000+8000] likely on CPU 1 (core 0, socket 0)

Xavier commented on 2024-03-29 12:56 (UTC)

Hi @GodofTheFallen, these types of issues should be reported to the Jetbrains bug tracker, unless you believe it is a packaging issue.

GodofTheFallen commented on 2024-03-28 04:34 (UTC)

There is an issue where the JetBrains window will steal the focus, and other windows above the JetBrains window will be passed through by the mouse. Pycharm's own dropdown bars and pop-up menus will also be passed through and cannot be clicked.

Ashark commented on 2024-02-27 13:29 (UTC)

@Xavier Finally! Thanks!

Xavier commented on 2024-02-18 17:58 (UTC)

@freso, that wrong path is dynamic, it depends on where you are building the package, so it is more complicated to just do a sed besides in future updates there could be more files (or not, we don´t know). Of course I prefer not to manipulate the file system outside the package manager, but we don't know the consequences of having wrong paths in the speed-up debugging.

Freso commented on 2024-02-18 17:25 (UTC)

With 4479465010ef2f6a58bc764b613e929daef79a6e (pkgrel=5) I get a hit on /usr/src/debug/pycharm-professional/pycharm-2023.3.3/plugins/python/helpers/pydev which doesn’t exist anywhere on my system.

This feels very similar to “WARNING: Package contains reference to $srcdir” (which I thought was what this was about at first, hence my grep’ing) and while I get that it may not be the neatest to have a "wrong" path in there, I’d argue that it’s way less neat to manipulate the file system outside of the package manager, especially if there is no confirmed issues arising from not doing so. If it turns out there is an issue, it should probably be filed as a bug with upstream. (I guess there’s always the option of sed -i 's|/usr/src/debug/pycharm-professional/pycharm-[0-9.]\+/|/opt/pycharm-professional/| or similar too…)

I’ll try and look into if there’s something that can be passed to build_ext to make it not include these paths, but even if not, I have a working PKGBUILD that doesn’t offend my sensibilities, so whether you choose to adopt any of my changes for that or not, it’ll only be a slight minor annoyance for me come update time if you don’t. :)