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: 238
Popularity: 2.74
First Submitted: 2013-09-25 03:56
Last Updated: 2021-01-28 02:44

Dependencies (29)

Required by (0)

Sources (4)

khenderick commented on 2014-01-17 07:43

Damnit, flagged out of date instead of just vote for it. Sorry for that

SoonerBourne commented on 2014-01-15 20:32


I am aware of this and it is part of the feedback I got from the submittal to the forums (comment dated 12/6/2013). As soon as JetBrains releases their next Pycharm, those changes will show up in the PKGBUILD file.

w1ntermute commented on 2014-01-15 19:53

The symlink the build script is creating in /usr/bin is incorrect. It's pointing to a relative path rather than an absolute one.

ln -s opt/$pkgname/bin/ usr/bin

should be:

ln -s /opt/$pkgname/bin/ usr/bin

SoonerBourne commented on 2014-01-14 17:14

The current install is for Pycharm 3.0.2 Build: 131.618 (Released: December 2, 2013)

SoonerBourne commented on 2014-01-14 17:12

This build is for Pycharm Professional version 3.0.2 Build: 131.618 (Jan. 14, 2014)

SoonerBourne commented on 2013-12-06 00:48

Yeah, I saw that too but didn't want to mark it as "2" since I didn't think that was the appropriate action.

I submitted the PKGBUILD file to the forum to see what other feedback I could get. So far I got a few items I'm getting corrected for the next release of PyCharm. I haven't been able to find a roadmap or release schedule from JetBrains, so who knows when the changes will show up here.

Psykar commented on 2013-12-05 22:46

Oh - unfortunately because your previous PKGBUILD had a pkgrel of 131.618, and you've just changed it to '1' it's not recognised as an update by pacman (and by extension, yaourt / packer etc)

Might have to save bumping the pkgrel back down to 1 until the next upstream release.

Psykar commented on 2013-12-05 22:42

Yeah no worries (I clicked out of date in a clicking frenzy and (of course) it's not possible to 'unclick' it)

I just happened to notice it when doing a namcap after the build.

Thanks for the quick fix :)

SoonerBourne commented on 2013-12-05 14:33


I don't think flagging a package out of date was the appropriate action given that the software WAS actually up to date.

However, I do appreciate the feedback and took over this package under the assumption that the original submitter had everything correct, which was possibly a bad assumption on my part. I have implemented the changes you requested. Testing locally both an upgrade and a clean install worked, so I pushed the change to here.

If you have any further suggestions please let me know in the comments or via email.


Psykar commented on 2013-12-05 04:49

This package creates an aboslute symbolic link which ends up pointing to the build directory:

lrwxrwxrwx 1 root root 111 Dec 5 15:39 /usr/bin/ -> /tmp/yaourt-tmp-louis/aur-pycharm-professional/pkg/pycharm-professional/opt/pycharm-professional/bin/

This line in the PKGBUILD needs fixing:
ln -s $pkgdir/opt/$pkgname/bin/ $pkgdir/usr/bin


cd $pkgdir
ln -s opt/$pkgname/bin/ usr/bin