Package Details: pycharm-community-eap 13:2022.2.222.2889.11-1

Git Clone URL: (read-only, click to copy)
Package Base: pycharm-community-eap
Description: Powerful Python and Django IDE, Early Access Program (EAP) build, Community Edition
Upstream URL:
Keywords: development early-access editor ide jetbrains python
Licenses: Apache
Conflicts: pycharm-community-edition
Provides: pycharm-community-edition
Submitter: flying-sheep
Maintainer: Kr1ss
Last Packager: Kr1ss
Votes: 14
Popularity: 0.003802
First Submitted: 2015-10-03 13:11 (UTC)
Last Updated: 2022-06-03 17:30 (UTC)

Latest Comments

Kr1ss commented on 2021-10-06 17:35 (UTC) (edited on 2021-10-06 17:36 (UTC) by Kr1ss)

As always, thx a lot for setting the flag @navarroaxel.

The EAP download links for both CE and Professional appear to be broken, hence why I don't update yet. Will check again tomorrow.

Cheers !

Kr1ss commented on 2021-02-05 20:58 (UTC) (edited on 2021-02-05 20:59 (UTC) by Kr1ss)

The current build uses the previous version of Jetbrains Runtime as a workaround for - hat tip @navarroaxel for pointing me to that bug, and solution.

RunAndTumble commented on 2020-08-28 13:44 (UTC)



The community version is absolutely terrible, seriously, I have no idea what the maintainers are doing. It depends on some outdated and incorrectly built packages resulting in those odd python2 dependencies (as well as gtk and qt). The whole chain has been marked as out-of-date a month ago but no result so far.

Kr1ss commented on 2020-08-27 14:20 (UTC)

The mandatory make dependency to python2-setuptools has been removed. If you want to have a precompiled Python 2 debugger included with the package, please make sure that python2-setuptools is installed before building pycharm-community-eap.

It won't be auto-installed and/or -removed any more by makepkg -sr.

Kr1ss commented on 2020-08-27 14:07 (UTC)

Sure @RunAndTumble, I hear you.

My intention is not to require python2 but also give users who need it the chance to include the compiled debugger in the package.

So I've implemented a build-time check for python2-setuptools being installed. If so, both Python 2 and 3 debuggers will be compiled and included, otherwise only the Python 3 one.

Not sure though if that's exactly the best way to go, especially regarding that community/pycharm-community still depends on python2-setuptools at build time.

Any thoughts are welcome. Thx.

P.S. Thx again @navarroaxel for pinging me when the new release came out :)

RunAndTumble commented on 2020-08-27 12:31 (UTC)

Don't you think you need to remove this python2 dependency completely? Or make it at least optional.

Kr1ss commented on 2020-01-29 11:33 (UTC)

Thank you for maintaining so far @flying-sheep !

Cheers !

@navarroaxel thx for the flag, gonna update tonight when back home.

flying-sheep commented on 2020-01-29 11:23 (UTC)

Hey, since I’m using professional edition for the time being, I’ll be handing this to Kr1ss fully.

Kr1ss commented on 2019-11-01 19:09 (UTC)

Fixed, thx for mentioning @sanerb.

sanerb commented on 2019-11-01 17:58 (UTC)

recommend you either add a conflicts for python-eap or name your binary to something like pycharm-ce-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.

Kr1ss commented on 2019-10-06 19:40 (UTC)

Yep indeed Jetbrains started shipping their own Java runtime with the IDE some time ago, we must've missed removing the dependency.

Thx @flixter for the hint.

flixter commented on 2019-10-06 18:30 (UTC)

Why is java-environment a dependency of this package? Quoting the requirements from PyCharm's download page: "Note: JetBrains Runtime (JBR) 11 is included with the PyCharm distribution. You do not need to install Java on your computer to run PyCharm."

Kr1ss commented on 2019-04-04 17:55 (UTC) (edited on 2019-04-04 19:38 (UTC) by Kr1ss)

Looks like you're trying to build in an Anaconda environment @syka.

I've just pushed a patch that uses absolute paths to the system python binaries, which should fix your problem.

syka commented on 2019-04-04 09:28 (UTC)

Error while installing:

creating build/lib.linux-x86_64-2.7 creating build/lib.linux-x86_64-2.7/_pydevd_bundle gcc -pthread -shared -B /home/syka/anaconda2/compiler_compat -L/home/syka/anaconda2/lib -Wl,-rpath=/home/syka/anaconda2/lib -Wl,--no-as-needed -Wl,--sysroot=/ -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-2.7/_pydevd_bundle/pydevd_cython.o -L/home/syka/anaconda2/lib -lpython2.7 -o build/lib.linux-x86_64-2.7/_pydevd_bundle/ /home/syka/anaconda2/compiler_compat/ld: build/temp.linux-x86_64-2.7/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info /home/syka/anaconda2/compiler_compat/ld: build/temp.linux-x86_64-2.7/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info /home/syka/anaconda2/compiler_compat/ld: build/temp.linux-x86_64-2.7/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info /home/syka/anaconda2/compiler_compat/ld: build/temp.linux-x86_64-2.7/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info build/temp.linux-x86_64-2.7/_pydevd_bundle/pydevd_cython.o: file not recognized: File format not recognized collect2: error: ld returned 1 exit status error: command 'gcc' failed with exit status 1 ==> ERROR: A failure occurred in build(). Aborting... Error making: pycharm-community-eap

Kr1ss commented on 2019-03-10 12:41 (UTC)

Well, that's neat. Thank you @flixter.

I'm just pushing a new pkgrel with your patch.

flixter commented on 2019-03-10 12:07 (UTC) (edited on 2019-03-10 12:07 (UTC) by flixter)

updating it with yaourt --aur causes a problem also because of the checksum. Question: As curl is already a dependency of pacman, why not stating only the IDE as a dependency, and then download on the fly the sha? Like:


sha256sums=($(curl -s "$_filever.tar.gz.sha256" | cut -d' ' -f1))

Kr1ss commented on 2018-12-12 11:14 (UTC) (edited on 2018-12-12 11:38 (UTC) by Kr1ss)

@gargan that's because we're downloading the checksum from the vendors site before building. When u call makepkg a second time after the source tarball and checksum has been loadad, the build will pass.

@chestm007 Yep you're right, the community repo version is called “pycharm-community-edition”. I'll adjust that tonight, thx.

gargan commented on 2018-12-12 02:10 (UTC)

Error while installing:

==> Making package: pycharm-community-eap 2:2018. (Tue 11 Dec 2018 09:08:11 PM EST) ==> Retrieving sources... -> Downloading pycharm-community-2018.3.1.tar.gz... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 154 100 154 0 0 267 0 --:--:-- --:--:-- --:--:-- 267 100 296M 100 296M 0 0 12.8M 0 0:00:23 0:00:23 --:--:-- 18.7M -> Downloading pycharm-community-2018.3.1.tar.gz.sha256... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 100 100 100 0 0 193 0 --:--:-- --:--:-- --:--:-- 193 ==> ERROR: Integrity checks (sha256) differ in size from the source array. Error downloading sources: pycharm-community-eap

chestm007 commented on 2018-12-12 02:04 (UTC)

I think you might need to change provides and conflicts to pycharm-community-edition. installing this didnt uninstall my previous installation of pycharm-community-edition from the community repo

Kr1ss commented on 2018-11-22 19:47 (UTC)

I'm pushing the final 2018.3 release even though this is an EAP package because community only has 2018.2.4 currently.

Kr1ss commented on 2018-10-22 22:18 (UTC)

Thx for reporting this @alt0160.

alt0160 commented on 2018-10-22 17:23 (UTC)

Can you add libdbusmenu-glib as a dependency?

Without it, PyCharm doesn't start: 'java.lang.UnsatisfiedLinkError: /opt/pycharm-community-eap/bin/ cannot open shared object file: No such file or directory'

Also reported here

Kr1ss commented on 2018-09-05 19:43 (UTC)

Great, thx for ur trust ! And here comes an update... :D

flying-sheep commented on 2018-09-02 14:55 (UTC)

Hi, thank you!

I’m updating it while writing this. Also I added you as co-maintainer.

Kr1ss commented on 2018-06-16 17:04 (UTC) (edited on 2018-08-26 19:18 (UTC) by Kr1ss)

I updated the build files to the current EAP version, which is 2018.2.1 (Build 182.3911.3) atm. Note that I had to introduce an epoch number because otherwise the newly added sub version number would confuse pacman's version sorting: 2018.2.182.3684.83-1 > 2018.2.1.3911.3-1

U can pull that if u like @flying-sheep :

EDIT - Thx for the update !

EDIT2 - Upstream has pushed some more updates in the meantime. Current build is 182.4323.5, which is 2018.2.3RC; have updated the GitLab repo.

notuxius commented on 2016-09-14 19:35 (UTC)

A small fix - Professional edition in description but this is Community edition

tovo commented on 2016-08-11 08:08 (UTC)

Thanks mate, It works when you run it twice.

flying-sheep commented on 2016-08-08 15:39 (UTC)

you have to run makepkg twice, sorry about that (the sha-extracting expression in the pkgbuild is evaluated before the file containing the hash is downloaded)

tovo commented on 2016-08-08 15:28 (UTC)

Hi there, I'm unable to upgrade my pycharm-community due to a failed integrity check : ==> ERROR: Integrity checks (sha256) differ in size from the source array. ==> ERROR: Makepkg was unable to build pycharm-community-eap. ==> Restart building pycharm-community-eap ? [y/N] ==> ---------------------------------------------- ==> ==> ERROR: unable to update I'm a alone ? Cheers

flying-sheep commented on 2016-01-31 22:16 (UTC)

well, pycharm-community is now at 5.0.4, so why use this? i’ll probably update this once it’s a preview for pycharm 6. but if you want you can take over, too!

gabor_bernat commented on 2016-01-25 10:01 (UTC)

Is this still on?

flying-sheep commented on 2015-11-01 17:41 (UTC)

will change it upon next release. making people redownload and -build for a description update seems overkill

flying-sheep commented on 2015-11-01 17:39 (UTC)

whoops, yeah!

xuiqzy commented on 2015-11-01 16:47 (UTC)

The description should probably say community edition ;)