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: | 239 |
Popularity: | 1.86 |
First Submitted: | 2013-09-25 03:56 |
Last Updated: | 2021-01-28 02:44 |
Dependencies (29)
- giflib
- glibc (glibc-linux4, glibc-git, glibc-force-mmap, lib32-glibc-force-mmap, glibc-minimal-git, glibc-dso, lib32-glibc-dso)
- 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
1 2 3 4 5 6 ... Next › Last »
XavierCLL commented on 2020-12-21 23:14
@edacval fixed, thanks
edacval commented on 2020-12-21 22:21
Build fails with :
install: cannot stat '/opt/pycharm-professional/bin/pycharm.png': No such file or directory
Fix:XavierCLL commented on 2020-12-21 21:04
@Singularity yeah I know that pixmap is deprecated I did it due to a request by one user but I think in the hicolor folder is the correct place, fixed, thanks. @nickb937 I checked it and I added some of them, nspr is provided by nss and jre-openjdk-headless is not necessary, this pycharm version uses the bundle package with JRE inside provided by them.
nickb937 commented on 2020-12-15 10:45
The following packages are required dependencies:
libxss, nspr, nssutil, jre-openjdk-headless
See: ldd /opt/pycharm-professional/jbr/lib/libjcef.so
hopter commented on 2020-12-11 10:41
why hardcoded the icon path in desktop file?
Singularity commented on 2020-12-08 19:24
I just looked over the last changes. You placed a link to the icon in /usr/share/pixmaps. However, you also hardcoded the icon path in the desktop files now. If you wouldn't do that, the icon theme could provide it's own icon, and the one from pixmaps would be used if it doesn't. Also, I think using the pixmaps directory is deprecated, /usr/share/icons/hicolor/scalable/apps/ is the new location.
PS: I also wouldn't hardcode the executable's path either, because then I can override it by placing my own in /usr/local/bin … (For example, I do that with java applications which still need java8, to set there a different JAVA_HOME and then calling the real binary from there.)
klaasjanelzinga commented on 2020-12-08 10:19
@donny thanks for the reply. I had cython installed and did a clean build. The problem was that I was working in a virtualenv. In this virtualenv there was no Cython installed.
So I deactivated and it worked, like a charm :)
donny commented on 2020-12-08 09:49
@klaasjanelzinga: Make sure your system is up to date (pacman -Suy) and
cython
package is installed (it's in makedepends), it's in the [community] repo. Also if you useyay
or some similar aur helper, do a clean build, don't re-use your old build files.klaasjanelzinga commented on 2020-12-08 09:36
Hi, I am getting an error when updating:
mqs commented on 2020-12-06 12:43
@XavierCLL thank you for the swift fix :)