Package Details: pycharm-professional 2024.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: custom
Submitter: hippojazz
Maintainer: Xavier (37h4n)
Last Packager: Xavier
Votes: 293
Popularity: 1.06
First Submitted: 2013-09-25 03:56 (UTC)
Last Updated: 2025-02-14 14:54 (UTC)

Dependencies (19)

Required by (0)

Sources (4)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 46 Next › Last »

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

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

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

jat255 commented on 2019-02-27 17:53 (UTC)

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)

karcher commented on 2019-01-19 12:37 (UTC)

I had the same issue like VikingofRock with anaconda. I did: $ pyenv shell system and then I could install it normally.

VikingofRock commented on 2019-01-10 02:31 (UTC) (edited on 2019-01-10 02:32 (UTC) by VikingofRock)

If anyone else is encountering an error like:

~/miniconda3/compiler_compat/ld: build/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
~/miniconda3/compiler_compat/ld: build/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
~/miniconda3/compiler_compat/ld: build/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
~/miniconda3/compiler_compat/ld: build/_pydevd_bundle/pydevd_cython.o: unable to initialize decompress status for section .debug_info
build/_pydevd_bundle/pydevd_cython.o: file not recognized: File format not recognized

The solution is to take miniconda off of your path before building pycharm-professional.

gilbus commented on 2018-12-05 20:28 (UTC)

Updated sums for 2018.3.1

diff --git a/PKGBUILD b/PKGBUILD
index 4f9fb3c..dd230cd 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,8 +1,8 @@
 # Maintainer: XavierCLL <xavier.corredor.llano (a) gmail.com>

 pkgname=pycharm-professional
-pkgver=2018.3.0
-_pkgver=2018.3
+pkgver=2018.3.1
+_pkgver=2018.3.1
 pkgrel=1
 pkgdesc="Powerful Python and Django IDE. Professional Edition."
 arch=('x86_64')
@@ -20,7 +20,7 @@ source=(https://download.jetbrains.com/python/$pkgname-$_pkgver.tar.gz
         'charm.desktop'
         'charm')
 # https://download.jetbrains.com/python/pycharm-professional-${_pkgver}.tar.gz.sha256
-sha256sums=('18f9018761e1f5488906e97c02a48a20d8c10a090d969f5e1107028f2d679a60'
+sha256sums=('5807c5409d4903183e263828d6b9285dfef13784308c577432758a16697a8a3c'
             'aaf7113e8c56e4d977eca204d57350d9493eda2710abefd2488a2b5d47c53344'
             '40b297ac1d883583ed5d7aae75fb09497a2af5bda9dd4aff83bd6d2892ab6c95'
             '818ed42f4200ae13315587abf6f247f93e68c658a94794f73924c985cdc145d0'

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 46 Next › Last »