Package Details: pycharm-professional 2020.3.3-1

Git Clone URL: (read-only, click to copy)
Package Base: pycharm-professional
Description: Python IDE for Professional Developers. Professional Edition
Upstream URL:
Keywords: development editor ide jetbrains python
Licenses: custom
Conflicts: pycharm, pycharm-community-edition
Provides: pycharm
Submitter: hippojazz
Maintainer: XavierCLL
Last Packager: XavierCLL
Votes: 239
Popularity: 1.71
First Submitted: 2013-09-25 03:56
Last Updated: 2021-01-28 02:44

Dependencies (29)

Required by (0)

Sources (4)

Latest Comments

« First ‹ Previous ... 4 5 6 7 8 9 10 11 12 13 14 ... Next › Last »

davidism commented on 2019-04-03 15:57

I flagged this package out of date with the mistaken comment that 2019.1.1 fixes the RST issue when using the system JDK. That's not correct, but you can still get the bundled JDK while using the AUR package, there's a plugin that lets you manage it within PyCharm. Official instructions:

wizpig64 commented on 2019-04-03 07:20

For anyone trying to fix PyCharm opening RST files, switch the preview panel renderer from JavaFX to Swing in Settings > Languages & Frameworks > ReStructured Text.

Source: David @

It looks like the JavaFX renderer was broken when this package switched off the bundled Java runtime onto the native system one. This is a repeat of another bug in 2017, something about font subpixel rendering 8 pages back. Eventually the repo switched back to bundled, and I no longer had to edit the PKGBUILD with every update. Now a bug appears, the switch is made again, and more bugs appear.

Switching to native Java in order to fix bugs seems to have a history of creating more bugs. Not to mention creating the work of having to manually edit PKGBUILDs!

@XavierCLL, what do you think of the idea of using two packages for this scenario? Something like pycharm-professional and pycharm-professional-native-java. Then if a user encounters a bug (like hidpi), they can find a pinned comment here saying to switch to the other branch?

From a user experience point of view, having the switch be made for us is destructive, and fiddling with PKGBUILDs and checksums is no fun when we'd rather be developing. I think it makes more sense for the AUR repo to have single opinion on the matter of its dependencies, especially when there are real tradeoffs between the versions. An alternate opinion belongs in another repo with provides: pycharm.

Thank you for spending your time maintaining this repo for the community!

lybin commented on 2019-04-02 01:40

I'm also have white border on windows with not native JBR KDE

Dreyk commented on 2019-04-01 19:03

@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.

XavierCLL commented on 2019-04-01 14:45

@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

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

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

XavierCLL commented on 2019-03-31 22:29

@lybin which functionality? how to reproduce that message?

XavierCLL commented on 2019-03-31 17:58

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


lybin commented on 2019-03-31 09:38 some functionality ask for native JBR