Search Criteria
Package Details: pycharm-professional 2020.3.3-1
| Git Clone URL: | https://aur.archlinux.org/pycharm-professional.git (read-only, click to copy) |
|---|---|
| Package Base: | pycharm-professional |
| Description: | Python IDE for Professional Developers. Professional Edition |
| Upstream URL: | https://www.jetbrains.com/pycharm/ |
| Keywords: | development editor ide jetbrains python |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| 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)
- giflib
- glibc (glibc-git)
- libdbusmenu-glib (libdbusmenu-glib-ubuntu)
- libxslt (libxslt-git)
- libxss
- libxtst
- nss (nss-hg)
- python (python-dbg)
- sh (bash-devel-git, dashbinsh, bash-devel-static-git, bash)
- cython (cython-kivy, cython-git) (make)
- python-setuptools (make)
- cython (cython-kivy, cython-git) (optional) – For performance debugger in Python 3
- cython2 (cython2-kivy) (optional) – For performance debugger in Python 2
- docker-compose (docker-compose-git, docker-compose-bin) (optional) – For support docker inside Pycharm
- docker-machine (optional) – For support docker inside Pycharm
- ipython (optional) – For enhanced interactive Python shell v3 inside Pycharm
- ipython2 (optional) – For enhanced interactive Python shell v2 inside Pycharm
- jupyter (optional) – For support Jupyter Notebook
- openssh (openssh-hpn-git, openssh-git, openssh-gssapi, openssh-selinux, openssh-hpn) (optional) – For deployment and remote connections
- python-coverage (optional) – For support code coverage measurement for Python 3
- python-pytest (optional) – For support testing inside Pycharm with Python 3
- python-setuptools (optional) – Packages manager for Python 3, for project interpreter
- python-tox (optional) – Python environments for testing tool with Python 3
- python2 (optional) – Python 2 support
- python2-coverage (optional) – For support code coverage measurement for Python 2
- python2-pytest (optional) – For support testing inside Pycharm with Python 2
- python2-setuptools (optional) – Packages manager for Python 2, for project interpreter
- python2-tox (optional) – Python environments for testing tool with Python 2
- vagrant (vagrant-git) (optional) – For support virtualized development environments
Latest Comments
« First ‹ Previous ... 22 23 24 25 26 27 28 29 Next › Last »
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
@w1ntermute
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/pycharm.sh usr/bin
should be:
ln -s /opt/$pkgname/bin/pycharm.sh 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
@Psykar
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.
Thanks!
Psykar commented on 2013-12-05 04:49
This package creates an aboslute symbolic link which ends up pointing to the build directory:
ie:
lrwxrwxrwx 1 root root 111 Dec 5 15:39 /usr/bin/pycharm.sh -> /tmp/yaourt-tmp-louis/aur-pycharm-professional/pkg/pycharm-professional/opt/pycharm-professional/bin/pycharm.sh
This line in the PKGBUILD needs fixing:
ln -s $pkgdir/opt/$pkgname/bin/pycharm.sh $pkgdir/usr/bin
to
cd $pkgdir
ln -s opt/$pkgname/bin/pycharm.sh usr/bin