Package Details: pycharm-professional 2024.3.1.1-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: 2.21
First Submitted: 2013-09-25 03:56 (UTC)
Last Updated: 2024-12-20 14:57 (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

1 2 3 4 5 6 .. 45 Next › Last »

Xavier commented on 2024-12-23 14:52 (UTC)

@0xc0ffee, I decided to change it because it was not only due to what you mentioned; other people also reported some problems with the post-script build. Originally, I included it in the post-script for reasons related to what you mentioned (specifically regarding the paths, which is why you can see a warning during the pkgbuild process). However, I believe this is not an issue, and they work well. These are binaries, and they are linked more to the Python/Cython versions than to the paths, unless someone reports or detects an issue related to this.

0xc0ffee commented on 2024-12-22 10:17 (UTC) (edited on 2024-12-22 12:00 (UTC) by 0xc0ffee)

@Xavier Thanks for the update.

Maybe I didn't express my idea clearly, but my point is that I'm pretty sure the error message that supply730 and I saw is a false alarm and it is benign. If you don't use pamac as your frontend for libalpm, you will not encounter that false alarm. I think the ideal fix here would be to submit a PR to Manjaro's pamac with better error detection logic.

JetBrains supplies pre-built Cython modules only for macOS and Windows, not for Linux. I am against the idea of lifting the Cython speedups job to packaging time. I know that in many cases the machine building this AUR package will also be the machine using it, but do we really want to make such an assumption? If there is any Python environment discrepancy between the packaging machine and the using machine, I'm worried those Cython modules may not work reliably. I believe this is one of the reasons why JetBrains wants Linux users to build those modules themselves.

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/*'

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

@0xc0ffee I prefer to compile the Cython speed up for the package rather than letting the user download it, but it is good to know that exist that option, thanks!. Due to some post-installation issues I moved the cython speed up into the PKGBUILD.

@Poscat @MikeBreytenbach for the next release I'm going to check that option, thanks.

0xc0ffee commented on 2024-12-17 02:14 (UTC)

@supply730 I encountered the same error while installing the built package using Manjaro's pamac manager. It seems the issue is specific to pamac, as neither libalpm nor pacman contain the language "Error while configuring <XXX>" in their source. I believe pamac will alarm if the keyword "error" presents in the output of the post-installation scriptlet (in this case, triggered by gcc's -Werror= flag): https://github.com/manjaro/libpamac/blob/49bfde599ed00c127869a2797b5bb26e28e11c2a/src/alpm_utils.vala#L2161

I see nothing wrong after the installation and those built products are there as expected. I got no alarm if I install the built package with pacman.

BTW, I think it's advisable to not include this process in the PKGBUILD, as those shared libraries are best built on the system running PyCharm. Otherwise JetBrains would have supplied those binaries in their release tarball: https://www.jetbrains.com/help/pycharm/cython-speedups.html

MikeBreytenbach commented on 2024-11-29 19:46 (UTC) (edited on 2024-11-29 19:48 (UTC) by MikeBreytenbach)

ChatGPT says it is possible to have PKGBUILD detect if the user has jdk21-jetbrains-bin installed, and if they do, offer them the option to use that instead of the bundled one:

if pacman -Q jdk21-jetbrains-bin > /dev/null 2>&1; then
  echo "Detected jdk21-jetbrains-bin. Would you like to use this instead of the bundled JetBrains JDK? (y/N)"
  read use_system_jdk
  if [[ $use_system_jdk == "y" || $use_system_jdk == "Y" ]]; then
    export JDK_PATH="/usr/lib/jvm/jdk21-jetbrains-bin"
  else
    export JDK_PATH="bundled_jdk_path"
  fi
fi

Xavier commented on 2024-11-29 19:29 (UTC)

@poscat sorry for my late response, I don't feel good about that idea, depending on another aur package managed by someone else, that could cause me to have to wait until they update this package for new releases, for instance, among other issues.

Poscat commented on 2024-11-22 04:36 (UTC)

Yes, but I'm using the package jdk21-jetbrains-bin for other jetbrains products.

Xavier commented on 2024-11-20 18:36 (UTC)

@postcat, It is not recommended at least for the professional version, Jetbrains applies several patches to the JDK, so it is better to use the JDK provided by them.

1 2 3 4 5 6 .. 45 Next › Last »