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.12
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 .. 13 14 15 16 17 18 19 20 21 22 23 .. 49 Next › Last »

montemedio commented on 2021-11-22 11:04 (UTC)

As of 2021.2.3, the package build fails for me with

ModuleNotFoundError: No module named 'Cython'
==> ERROR: A failure occurred in build().
    Aborting...

Xavier commented on 2021-10-28 19:00 (UTC) (edited on 2021-10-28 19:09 (UTC) by Xavier)

Hi @franga2000 for me the debugging works without problems with libffi from core repo, what is your error? I don't like to add aur depend even more if I cannot confirm the problem...

franga2000 commented on 2021-10-28 09:03 (UTC)

The libffi package no longer includes the ABI v7 compatibility library (see [0]), but I can't get the PyCharm debugger running without it. Installing aur/libffi7 fixes it, so this package should probably depend on it.

[0] https://github.com/archlinux/svntogit-packages/commit/856bd5b52222f1456334e0a08c13e58bdfda9db0#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a

Xavier commented on 2021-09-19 00:46 (UTC) (edited on 2021-09-19 00:46 (UTC) by Xavier)

Hi @olii, good catch thanks, the best is to build it running the script, fixed.

olii commented on 2021-09-18 16:52 (UTC)

After install, when trying to attach the debugger to a running Python process I get the following error:

RuntimeError: Could not find dll file to inject: /opt/pycharm-professional/plugins/python/helpers/pydev/pydevd_attach_to_process/attach_linux_amd64.so

I noticed that the .so library is in the original package but the library is deleted in the build process:

find pycharm-${pkgver}/plugins/python/helpers/pydev/ \( -name *.so -o -name *.pyd \) -delete

I think that we should either leave libraries in pydevd_attach_to_process untouched or rebuild them by the script located in:

/opt/pycharm-professional/plugins/python/helpers/pydev/pydevd_attach_to_process/linux_and_mac/compile_linux.sh

What do you think?

klaasjanelzinga commented on 2021-08-28 11:08 (UTC)

@donny, thanks for the suggestion. I deleted my comment. With the PKGEXT var set it goes much better.

donny commented on 2021-08-28 11:04 (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'.

Xavier commented on 2021-08-27 19:09 (UTC)

good catch @alorence, fixed in the new release, thanks

alorence commented on 2021-07-30 10:01 (UTC) (edited on 2021-07-30 10:04 (UTC) by alorence)

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

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 49 Next › Last »