Package Details: pycharm 2026.2-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.08
First Submitted: 2025-10-04 18:47 (UTC)
Last Updated: 2026-07-22 13:03 (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 .. 24 25 26 27 28 29 30 31 32 33 34 .. 49 Next › Last »

Dreyk commented on 2019-04-01 19:03 (UTC) (edited on 2019-04-01 19:15 (UTC) by Dreyk)

@XavierCLL In my opinion, JetBrains has reasons to use its own java runtime implementation. And I use Manjaro Linux, not an Arch Linux, so I don’t want to keep track of additional dependencies. And with the random next update, their unexpected incompatibility (system java and PyCharm) can lead to problems that can be avoided if just do not complicate these things. In addition, I do not have HiDPI displays... Therefore, this did not affect me. But I hope that this bug will be fixed and you will be able to release the next version with JBR as before.

Xavier commented on 2019-04-01 14:45 (UTC)

@lybin yes, but that is not literally an error, however, if there are more troubles and if JBR fix the HiPDI error in the next release, maybe I will return to JBR version.

@dreyk not, the install file is not related with JBR, but why do you want to use the JBR version?

Dreyk commented on 2019-04-01 12:45 (UTC) (edited on 2019-04-01 12:46 (UTC) by Dreyk)

To use this update with JBR I only need to delete java-runtime dependency, remove the 'no-jbr' in link and update checksums in PKGBUILD file? I am not familiar with AUR packages and PKGBUILD, but why did you delete the "install=${pkgname}.install" line in this update? This is not related to "no-jbr" edition?

In any case, thanks for your work.

lybin commented on 2019-04-01 05:53 (UTC)

@XavierCLL, e.g. CTRL+SHIFT+F on tree left side

Xavier commented on 2019-03-31 22:29 (UTC)

@lybin which functionality? how to reproduce that message?

Xavier commented on 2019-03-31 17:58 (UTC)

This update use the no-jbr package (not bundled JRE) due to problems with hipdi [1] and if it works fine is prefer to use the native java of Archlinux, if you want use bundled JRE (JBR): delete java-runtime deps, remove the 'no-jbr' in link and update sums

[1] https://youtrack.jetbrains.com/issue/IDEA-209811

lybin commented on 2019-03-31 09:38 (UTC)

https://i.imgur.com/drx01Io.png some functionality ask for native JBR

Dreyk commented on 2019-03-31 09:11 (UTC) (edited on 2019-03-31 09:13 (UTC) by Dreyk)

Hello. The following updates will be with JBR? I would like to use native JBR for PyCharm... It means, I need to modify PKGBUILD according to older versions?

Obliviadge commented on 2019-03-29 12:24 (UTC) (edited on 2019-03-29 12:24 (UTC) by Obliviadge)

The sha256 sum for the 2019.1 charm is incorrect I think. I used: f23c1c7e63d9a8b9ae2e2c6139bb77cd7a6e6eb32ad22f47c74d9daca9a891d1

« First ‹ Previous 1 .. 24 25 26 27 28 29 30 31 32 33 34 .. 49 Next › Last »