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 .. 7 8 9 10 11 12 13 14 15 16 17 .. 49 Next › Last »

lybin commented on 2023-04-20 09:43 (UTC)

@Xavier, do you have direct links on bugs which block us to upgrade? let's go to vote to speed up.

leandrocunha commented on 2023-04-14 21:51 (UTC) (edited on 2023-04-14 21:53 (UTC) by leandrocunha)

I did a test and it seems that the most current version has some problems causing the machine to freeze for a while and it returns to normal in minutes in Arch. On a Windows machine I haven't had any problems so far and it's a much better machine where, if there's a memory leak, you wouldn't notice. I did downgrade version to 2022.3.3.

<deleted-account> commented on 2023-04-03 10:52 (UTC)

Thank you @Xavier for uploading the files for the latest version.

For those of us that want to have the latest version, but are unable or unwilling to build the project, I should mention that you can also download PyCharm 2023.1 from the "JetBrains Toolbox" program, available on the AUR under the name jetbrains-toolbox. It provides a "one-click install" for all JetBrains products, even for multiple versions of it at once!

But the same issues reported by Xavier remain, so do it at your own risk :)

ZorinArch commented on 2023-04-01 19:25 (UTC) (edited on 2023-04-01 19:26 (UTC) by ZorinArch)

i try this steps and pycharm works fine with me till now:

  1. Delete charm script from /usr/bin/charm.py
  2. Rename "charm" to "pycharm" in desktop file charm.desktop -> pycharm.desktop any charm rename it to pycharm
  3. sudo ln -s /opt/pycharm/bin/pycharm.sh /usr/local/bin/pycharm. check this: https://www.jetbrains.com/help/pycharm/working-with-the-ide-features-from-command-line.html#cdce0ebd

i hope this help.

CaeZaR commented on 2023-04-01 18:46 (UTC)

Is it possible to commit the 2023.1 changes to a branch so that those who want to test it out can clone and run the build themselves? I have tried testing it out myself and I agree there are still some UI bugs. I also don't know what to do about the warning I'm getting: "Obsolete launcher script found." If you have a solution to the last problem @Xavier, I'd be interested to know what that is.

Xavier commented on 2023-04-01 17:54 (UTC)

There is not only the issue I reported, there are some others bugs and regressions related to the new release. IMHO I use this IDE on a daily basis so I prefer stability, the best thing here is to wait at least for the first patch. @zappaboy can do it manually but this release requires other adjustments in the pkgbuild

lybin commented on 2023-04-01 11:47 (UTC)

@zappaboy, you can if you can't to wait (:

ZappaBoy commented on 2023-04-01 08:30 (UTC)

Anyone can update to "pkgver=2022.3.3" to "pkgver=2023.1" ?

tocic commented on 2023-03-31 05:34 (UTC)

Thank you for the maintenance. Here is the issue to track.

« First ‹ Previous 1 .. 7 8 9 10 11 12 13 14 15 16 17 .. 49 Next › Last »