Package Details: pycharm-professional 2019.1.2-1

Git Clone URL: https://aur.archlinux.org/pycharm-professional.git (read-only)
Package Base: pycharm-professional
Description: Powerful Python and Django IDE. Professional Edition.
Upstream URL: https://www.jetbrains.com/pycharm/
Keywords: development editor ide jetbrains python
Licenses: custom
Conflicts: pycharm, pycharm-community-edition
Provides: pycharm
Submitter: hippojazz
Maintainer: XavierCLL
Last Packager: XavierCLL
Votes: 208
Popularity: 6.280658
First Submitted: 2013-09-25 03:56
Last Updated: 2019-05-08 15:55

Dependencies (26)

Required by (0)

Sources (5)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

Dreyk commented on 2019-04-01 19:03

@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.

XavierCLL commented on 2019-04-01 14:45

@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

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

@XavierCLL, e.g. CTRL+SHIFT+F on tree left side

XavierCLL commented on 2019-03-31 22:29

@lybin which functionality? how to reproduce that message?

XavierCLL commented on 2019-03-31 17:58

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

[1] https://youtrack.jetbrains.com/issue/IDEA-209811

lybin commented on 2019-03-31 09:38

https://i.imgur.com/drx01Io.png some functionality ask for native JBR

Dreyk commented on 2019-03-31 09:11

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

The sha256 sum for the 2019.1 charm is incorrect I think. I used: f23c1c7e63d9a8b9ae2e2c6139bb77cd7a6e6eb32ad22f47c74d9daca9a891d1

jat255 commented on 2019-02-27 17:53

Related to what @VikingofRock posted, has anyone using this package been able to install the Cython debugging extensions in a project that is using a conda environment as the Python interpreter? The extensions compile fine when using the system-wide python, but fail when using conda's python. I receive the following error when trying to compile the extensions manually:

$ sudo /path/to/miniconda/python /opt/pycharm-professional/helpers/pydev/setup_cython.py build_ext --inplace

running build_ext
building '_pydevd_bundle.pydevd_cython' extension
creating build/temp.linux-x86_64-3.6
creating build/temp.linux-x86_64-3.6/_pydevd_bundle
gcc -pthread -B /home/xxx/.conda/envs/xxx/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/xxx/.conda/envs/xxx/include/python3.6m -c _pydevd_bundle/pydevd_cython.c -o build/temp.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.o
creating build/lib.linux-x86_64-3.6
creating build/lib.linux-x86_64-3.6/_pydevd_bundle
gcc -pthread -shared -B /home/xxx/.conda/envs/xxx/compiler_compat -L/home/xxx/.conda/envs/xxx/lib -Wl,-rpath=/home/xxx/.conda/envs/xxx/lib -Wl,--no-as-needed -Wl,--sysroot=/ build/temp.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.o -o build/lib.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.cpython-36m-x86_64-linux-gnu.so
/home/xxx/.conda/envs/xxx/compiler_compat/ld: build/temp.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
/home/xxx/.conda/envs/xxx/compiler_compat/ld: build/temp.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
/home/xxx/.conda/envs/xxx/compiler_compat/ld: build/temp.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
/home/xxx/.conda/envs/xxx/compiler_compat/ld: build/temp.linux-x86_64-3.6/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
build/temp.linux-x86_64-3.6/_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

(x-posting this comment to the miniconda3 AUR page)