Package Details: pycharm-professional 2024.3.2-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.73
First Submitted: 2013-09-25 03:56 (UTC)
Last Updated: 2025-01-28 12:53 (UTC)

Dependencies (19)

Required by (0)

Sources (4)

Pinned Comments

Xavier commented on 2024-12-20 15:15 (UTC)

MANUAL INTERVENTION FOR v2024.3.1.1:

Due to the latest changes for the cython speed up, this release is going to show a commit transaction conflicting files, to fix this you need to enable Cython Speed ​​Up file overwriting:

[aur helper] pycharm-professional --overwrite '/opt/pycharm-professional/plugins/python-ce/helpers/pydev/*'

or after manual build:

sudo pacman -U pycharm-professional-2024.3.1.1-1-x86_64.pkg.tar.zst --overwrite '/opt/pycharm-professional/plugins/python-ce/helpers/pydev/*'

Latest Comments

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 45 Next › Last »

Xavier commented on 2021-10-28 19:00 (UTC) (edited on 2021-10-28 19:09 (UTC) by Xavier)

Hi @franga2000 for me the debugging works without problems with libffi from core repo, what is your error? I don't like to add aur depend even more if I cannot confirm the problem...

franga2000 commented on 2021-10-28 09:03 (UTC)

The libffi package no longer includes the ABI v7 compatibility library (see [0]), but I can't get the PyCharm debugger running without it. Installing aur/libffi7 fixes it, so this package should probably depend on it.

[0] https://github.com/archlinux/svntogit-packages/commit/856bd5b52222f1456334e0a08c13e58bdfda9db0#diff-3e341d2d9c67be01819b25b25d5e53ea3cdf3a38d28846cda85a195eb9b7203a

Xavier commented on 2021-09-19 00:46 (UTC) (edited on 2021-09-19 00:46 (UTC) by Xavier)

Hi @olii, good catch thanks, the best is to build it running the script, fixed.

olii commented on 2021-09-18 16:52 (UTC)

After install, when trying to attach the debugger to a running Python process I get the following error:

RuntimeError: Could not find dll file to inject: /opt/pycharm-professional/plugins/python/helpers/pydev/pydevd_attach_to_process/attach_linux_amd64.so

I noticed that the .so library is in the original package but the library is deleted in the build process:

find pycharm-${pkgver}/plugins/python/helpers/pydev/ \( -name *.so -o -name *.pyd \) -delete

I think that we should either leave libraries in pydevd_attach_to_process untouched or rebuild them by the script located in:

/opt/pycharm-professional/plugins/python/helpers/pydev/pydevd_attach_to_process/linux_and_mac/compile_linux.sh

What do you think?

klaasjanelzinga commented on 2021-08-28 11:08 (UTC)

@donny, thanks for the suggestion. I deleted my comment. With the PKGEXT var set it goes much better.

donny commented on 2021-08-28 11:04 (UTC)

@XavierCLL Please don't do what @klaasjanelzinga suggests. Not only it's wrong place to set the XZ_OPT env.var., it also doesn't have any effect on the package build speed, because XZ is not involved since January 2020.

@klaasjanelzinga If you build packages just for yourself, you can omit package compression simply by changing the line PKGEXT='.pkg.tar.zst' (or maybe .pkg.tar.xz still in your case) to PKGEXT='.pkg.tar'.

Xavier commented on 2021-08-27 19:09 (UTC)

good catch @alorence, fixed in the new release, thanks

alorence commented on 2021-07-30 10:01 (UTC) (edited on 2021-07-30 10:04 (UTC) by alorence)

I recently encountered issues to build Cython extension for a project using python 3.6, installed using pyenv, while my system use python3.9 by default. The error was easily reproducible in console, and was related to missing _pydevd_frame_eval/pydevd_frame_evaluator.c in pydevd folder.

I noticed that the PKGBUILD run

find pycharm-${pkgver}/plugins/python/helpers/pydev/ \( -name *.c -o -name *.so -o -name *.pyd \) -delete

as first command in the build step. While I understand that *.so and *.pyd files may be deleted before building, I don't understand why *.c files are deleted too. Is it an error ?

By the way I edited the PKGBUILD before building the package to remove *.c files deletion, and I was able to build Cython extension for my py3.6 project

find pycharm-${pkgver}/plugins/python/helpers/pydev/ \( -name *.so -o -name *.pyd \) -delete

Brikowski commented on 2021-05-24 08:29 (UTC) (edited on 2021-05-25 16:59 (UTC) by Brikowski)

I also had the problem "ModuleNotFoundError: No module named 'Cython'" when building from the terminal with Pamac on Manjaro. However, I had a conda virtual environment activated.

The build finished successfully for me when using Pamac GUI.

« First ‹ Previous 1 .. 9 10 11 12 13 14 15 16 17 18 19 .. 45 Next › Last »