@XavierCLL In my opinion, JetBrains has reasons to use its own java runtime implementation. And I use Manjaro Linux, not an Arch Linux, so I don’t want to keep track of additional dependencies. And with the random next update, their unexpected incompatibility (system java and PyCharm) can lead to problems that can be avoided if just do not complicate these things. In addition, I do not have HiDPI displays... Therefore, this did not affect me. But I hope that this bug will be fixed and you will be able to release the next version with JBR as before.
Search Criteria
Package Details: pycharm-professional 2024.3-1
Package Actions
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: | custom |
Submitter: | hippojazz |
Maintainer: | Xavier (37h4n) |
Last Packager: | Xavier |
Votes: | 289 |
Popularity: | 1.07 |
First Submitted: | 2013-09-25 03:56 (UTC) |
Last Updated: | 2024-11-14 03:02 (UTC) |
Dependencies (19)
- cython (cython-gitAUR, cython0AUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- giflib (giflib-gitAUR)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR, glibc-eac-binAUR, glibc-eac-rocoAUR)
- libdbusmenu-glib
- python (python37AUR, python311AUR, python310AUR)
- python-setuptools
- sh (dashbinshAUR, bash-devel-static-gitAUR, zshbinshAUR, bash-devel-gitAUR, busybox-coreutilsAUR, bash-gitAUR, bash)
- ttf-font (neuropol-ttfAUR, ttf-win7-fontsAUR, ttf-ms-win8AUR, ttf-ms-win8-arabicAUR, ttf-ms-win8-hebrewAUR, ttf-ms-win8-seaAUR, ttf-ms-win8-indicAUR, ttf-ms-win8-japaneseAUR, ttf-ms-win8-koreanAUR, ttf-ms-win8-zh_cnAUR, ttf-ms-win8-zh_twAUR, ttf-ms-win8-thaiAUR, ttf-ms-win8-otherAUR, ttf-kidsAUR, ttf-liberation-sans-narrowAUR, ttf-cavafy-scriptAUR, ttf-ms-fontsAUR, ttf-dejavu-ibAUR, ttf-zeldaAUR, ttf-oxygenAUR, ttf-oxygen-gfAUR, ttf-share-gfAUR, ttf-gostAUR, otf-inconsolata-dzAUR, ttf-d2codingAUR, ttf-agaveAUR, ttf-caracteresAUR, ttf-cuprumAUR, ttf-autour-oneAUR, ttf-impallari-milongaAUR, ttf-impallari-miltonianAUR, ttf-clarity-cityAUR, ttf-ms-win10AUR, ttf-ms-win10-japaneseAUR, ttf-ms-win10-koreanAUR, ttf-ms-win10-seaAUR, ttf-ms-win10-thaiAUR, ttf-ms-win10-zh_cnAUR, ttf-ms-win10-zh_twAUR, ttf-ms-win10-otherAUR, ttf-win10AUR, ttf-ms-win10-cdnAUR, ttf-bmonoAUR, ttf-pt-astra-factAUR, ttf-weblysleekuiAUR, ttf-pt-astra-sansAUR, ttf-pt-astra-serifAUR, ttf-pt-sansAUR, ttf-pt-serifAUR, ttf-pt-monoAUR, ttf-pt-root_uiAUR, ttf-xo-fontsAUR, noto-fonts-liteAUR, ttf-paratypeAUR, ttf-plemoljp-binAUR, ttf-dejavu-emojilessAUR, noto-fonts-variable-liteAUR, ttf-lucida-fontsAUR, ttf-plemoljpAUR, ttf-juiseeAUR, ttf-ms-win10-autoAUR, ttf-karlaAUR, noto-fonts-latin-greek-cyrillicAUR, apple-fontsAUR, ttf-noto-sans-vfAUR, ttf-noto-serif-vfAUR, ttf-noto-sans-mono-vfAUR, ttf-ms-win11AUR, ttf-ms-win11-japaneseAUR, ttf-ms-win11-koreanAUR, ttf-ms-win11-seaAUR, ttf-ms-win11-thaiAUR, ttf-ms-win11-zh_cnAUR, ttf-ms-win11-zh_twAUR, ttf-ms-win11-otherAUR, ttf-ms-win11-autoAUR, gnu-free-fonts, noto-fonts, ttf-bitstream-vera, ttf-croscore, ttf-dejavu, ttf-droid, ttf-ibm-plex, ttf-input, ttf-input-nerd, ttf-liberation)
- docker-compose (docker-compose-v1-binAUR, docker-compose-gitAUR, docker-desktopAUR) (optional) – For support docker inside Pycharm
- docker-machine (docker-machine-gitlab-binAUR) (optional) – For support docker inside Pycharm
- ipython (ipython-gitAUR) (optional) – For enhanced interactive Python shell inside Pycharm
- jupyter-server (optional) – For Jupyter notebooks and apps
- openssh (openssh-gitAUR, openssh-dotconfigAUR, openssh-dotconfig-binAUR, openssh-selinuxAUR, openssh-hpn-shimAUR, openssh-gssapiAUR) (optional) – For deployment and remote connections
- python-coverage (optional) – For support code coverage measurement
- python-pytest (optional) – For support testing inside Pycharm
- python-setuptools (optional) – Packages manager for Python, for project interpreter
- python-tox (optional) – Python environments for testing tool
- vagrant (vagrant-gitAUR) (optional) – For support virtualized development environments
Required by (0)
Sources (4)
Latest Comments
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 44 Next › Last »
Dreyk commented on 2019-04-01 19:03 (UTC) (edited on 2019-04-01 19:15 (UTC) by Dreyk)
Xavier commented on 2019-04-01 14:45 (UTC)
@lybin yes, but that is not literally an error, however, if there are more troubles and if JBR fix the HiPDI error in the next release, maybe I will return to JBR version.
@dreyk not, the install file is not related with JBR, but why do you want to use the JBR version?
Dreyk commented on 2019-04-01 12:45 (UTC) (edited on 2019-04-01 12:46 (UTC) by Dreyk)
To use this update with JBR I only need to delete java-runtime dependency, remove the 'no-jbr' in link and update checksums in PKGBUILD file? I am not familiar with AUR packages and PKGBUILD, but why did you delete the "install=${pkgname}.install" line in this update? This is not related to "no-jbr" edition?
In any case, thanks for your work.
lybin commented on 2019-04-01 05:53 (UTC)
@XavierCLL, e.g. CTRL+SHIFT+F on tree left side
Xavier commented on 2019-03-31 22:29 (UTC)
@lybin which functionality? how to reproduce that message?
Xavier commented on 2019-03-31 17:58 (UTC)
This update use the no-jbr package (not bundled JRE) due to problems with hipdi [1] and if it works fine is prefer to use the native java of Archlinux, if you want use bundled JRE (JBR): delete java-runtime deps, remove the 'no-jbr' in link and update sums
lybin commented on 2019-03-31 09:38 (UTC)
https://i.imgur.com/drx01Io.png some functionality ask for native JBR
Dreyk commented on 2019-03-31 09:11 (UTC) (edited on 2019-03-31 09:13 (UTC) by Dreyk)
Hello. The following updates will be with JBR? I would like to use native JBR for PyCharm... It means, I need to modify PKGBUILD according to older versions?
Obliviadge commented on 2019-03-29 12:24 (UTC) (edited on 2019-03-29 12:24 (UTC) by Obliviadge)
The sha256 sum for the 2019.1 charm is incorrect I think. I used: f23c1c7e63d9a8b9ae2e2c6139bb77cd7a6e6eb32ad22f47c74d9daca9a891d1
Pinned Comments