Package Details: pycharm-eap 2022.3.223.4884.74-1

Git Clone URL: (read-only, click to copy)
Package Base: pycharm-eap
Description: Powerful Python and Django IDE, Early Access Program (EAP) build. Professional edition.
Upstream URL:
Keywords: development editor ide jetbrains python
Licenses: custom
Provides: pycharm, pycharm-professional
Submitter: vlan
Maintainer: qft
Last Packager: qft
Votes: 31
Popularity: 0.020931
First Submitted: 2011-05-06 08:33 (UTC)
Last Updated: 2022-09-24 00:49 (UTC)

Dependencies (18)

Required by (0)

Sources (2)

Latest Comments

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

sausix commented on 2021-08-15 19:55 (UTC)

The "nextversion" link is quite broken.

Just found a new link which already offers a newer version of pycharm-eap.

So this package is practically outdated then.

Thank you.

artafinde commented on 2021-05-17 14:39 (UTC)

I'm against epoch in general since then you have to carry this on every upgrade.. It's not a big thing for me just worth mentioning in case other had that issue. (you do get a notification anyway from PyCharm itself).

Kr1ss commented on 2021-05-17 13:55 (UTC) (edited on 2021-05-17 14:01 (UTC) by Kr1ss)

@artafinde @qft

It's not about the number of dots.

In this case, 2021.1.211.6693.115-1 is deemed greater than 2021. because 211 is greater than 1 :

2021. 1.211. [...]
2021. 1.  1. [...]

I guess @qft could intruduce an epoch. At least that's what I do with pycharm-community-eap.

Cheers !

(EDIT/ visualization added)

artafinde commented on 2021-05-17 13:41 (UTC)

qft: the pkgver defined in this package doesn't work with pacman's comparison so some new versions don't appear.. Example:

loading packages...
warning: downgrading package pycharm-eap (2021.1.211.6693.115-1 => 2021.

Clearly this is an update but pacman thinks it's downgrading. My assumption is the comparison in pacman doesn't detect so many dots? :/

Kr1ss commented on 2021-02-06 22:35 (UTC)

NP. Guess we both need to thank @navarroaxel, who made me aware of this issue in the first place. :)

qft commented on 2021-02-06 22:32 (UTC)

@Kr1ss thank you very much for pointing this out! I just updated the PKGBUILD as you suggested and the issue appears to be fixed for now.

Kr1ss commented on 2021-02-06 21:47 (UTC) (edited on 2021-02-06 21:47 (UTC) by Kr1ss)

@qft There's a bug in the current JBR causing it to crash - see

Essentially, you need to use the previous version (211.4961.30), and install it in place.

For PKGBUILD examples, see latest commits of pycharm-cummunity-eap or webstorm-eap

Cheers !

petris commented on 2020-12-05 17:20 (UTC)

@qft Great, thanks!

qft commented on 2020-12-05 04:25 (UTC)

@petris Apart from compiling the debugger speedup extension, I don't think cython is used directly by the PyCharm IDE. (Even compiling the debugger speedup extension did not require the cython compiler previously, as the .c source code was pre-cythonized by JetBrains. It only becomes required in build 203.5981.52 because of the bug, thus the previous reason for making cython an optional dependency "For performance debugger in Python" was incorrect to begin with). PyCharm can edit cython source files, but it does not have a built-in way of calling the cython compiler, thus I don't think the cython compiler is a dependency of the IDE.

petris commented on 2020-12-05 03:41 (UTC)

@qft I think that cython should also be left as an optional dependency though, since you'd still need it for some things after building, right?

Also, thank you.