Package Details: pycharm-professional 2019.1.3-1

Git Clone URL: (read-only)
Package Base: pycharm-professional
Description: Powerful Python and Django IDE. 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: 209
Popularity: 4.644963
First Submitted: 2013-09-25 03:56
Last Updated: 2019-06-03 21:40

Dependencies (27)

Required by (0)

Sources (5)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

XavierCLL commented on 2019-06-03 21:42

@nicoulaj good idea, added, thanks

nicoulaj commented on 2019-06-03 19:05

Another little thing, could you add /opt/pycharm-professional/bin/ to backup since we already have the vmoptions files ?

XavierCLL commented on 2019-05-26 23:26

Thanks @nicoulaj, added for the next release.

nicoulaj commented on 2019-05-26 17:11

The package could have an optdepends on python-docutils-stubs, pycharm asks for it when using sphynx.

XavierCLL commented on 2019-05-08 15:58

The problem with HiDPI displays was fixed with this release 2019.1.2

Dreyk commented on 2019-04-09 09:18

Thank you for coming back PyCharm with JBR!

XavierCLL commented on 2019-04-03 21:22

If someone wants to use the Java of the system (no JBR) using this package, is easy after install run sudo rm -rf /opt/pycharm-professional/jre64

XavierCLL commented on 2019-04-03 20:59

@ilinojkovic check if the old package is in /var/cache/pacman/pkg/, else you need to build manually with makepkg, if you need more help use the wikis or forums.

ilinojkovic commented on 2019-04-03 19:42

@XavierCLL Thanks for the response! I changed the settings as instructed, but I'm not quite satisfied with the results. What is the smoothest way to downgrade to 2018.3.5? Preferably using pacman/yay (arch newbie here btw)

XavierCLL commented on 2019-04-03 18:36

Thanks for your comments guys, @wizpig64 I consider that pycharm-professional must use the JBR, due that JetBrains apply several patches to the original JDK then I don't think necessary have another package like *-native-java (but it is open if you want), I changed it temporally to no-JBR for fix some problems, but I'm seeing that no-JBR come with other problems, I'm sorry for the inconveniences.

I expect that the issues relate with HiPDI will fix soon (not for the 2019.1.1) JetBrains are aware of it [1]

In the correct order to update this package, I should not update to 2019 until JetBrain fix the issues with HiPDI, but considering that this affected few people and being democratic, I just updated it to 2019.1.1 with JBR.

In HiPDI displays (not in all case) is possible to correctly adjust using -Dide.ui.scale=xx and font size in the IDE. @ilinojkovic for that read [2]

[1] [2]