Package Details: pycharm-eap 2020.

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: 28
Popularity: 0.000791
First Submitted: 2011-05-06 08:33
Last Updated: 2021-01-02 00:08

Dependencies (18)

Required by (0)

Sources (2)

Latest Comments

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

petris commented on 2020-12-05 17:20

@qft Great, thanks!

qft commented on 2020-12-05 04:25

@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

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

qft commented on 2020-12-04 17:28

@petris, sorry for the issue, it's fixed now.

petris commented on 2020-12-04 04:39

2020.3 does not build in a clean chroot. cython is now required as a makedepends.

qft commented on 2019-11-02 18:24

@sanerb @Kr1ss Thank you for pointing this out and the change in pycharm-community-eap.

Kr1ss commented on 2019-11-01 18:55

Never mind @qft, I'm about to rename the starter link of pycharm-community-eap to /usr/bin/pycharm-ce, to prevent that conflict.

Thx @sanerb for pointing this out.

sanerb commented on 2019-11-01 17:58

recommend you either add a conflicts for python-community-eap or name your binary to something like pycharm-pro-eap; you're both using the same binary path (/usr/bin/pycharm-eap) and according to upstream, both should be able to be co-installed. that's the only file conflict since you install to different /opt dirs.

mitchhentges commented on 2019-01-09 17:55

Just a heads up that the current published version has the ".3" twice, causing package managers not to update.

My current version: 2018.3.183.4284.139-1 Published version: 2018.

183 > 3, so it won't upgrade :)

qft commented on 2017-10-20 17:15

The current PKGBUILD already works for both the EAP and the regular PyCharm. For example, and points to exactly the same file. Thus there is no need to specify two link formats.

As for the automatic downloading of the checksum. I find the additional wget clause to be not as clean as putting the .sha256 file inside the ${source}. However putting the .sha256 file inside ${source} requires running the makepkg command twice, which is even uglier. What's the benefit to end users if the .sha256 file is dynamically updated instead of hard-coded in the ${sha256sums} field?