Hi folk!
I'm renaming/merging this package pycharm-professional into pycharm. See more:
https://blog.jetbrains.com/pycharm/2025/04/unified-pycharm/ https://gitlab.archlinux.org/archlinux/packaging/packages/pycharm-community-edition/-/issues/8
| Git Clone URL: | https://aur.archlinux.org/pycharm.git (read-only, click to copy) |
|---|---|
| Package Base: | pycharm |
| Description: | The only Python IDE you need. Bundled with the official JetBrains Runtime (JBR) |
| Upstream URL: | https://www.jetbrains.com/pycharm/ |
| Licenses: | custom |
| Conflicts: | pycharm-community-edition, pycharm-professional |
| Provides: | pycharm |
| Replaces: | pycharm-professional |
| Submitter: | Xavier |
| Maintainer: | Xavier |
| Last Packager: | Xavier |
| Votes: | 300 |
| Popularity: | 4.05 |
| First Submitted: | 2025-10-04 18:47 (UTC) |
| Last Updated: | 2025-10-24 22:12 (UTC) |
Hi folk!
I'm renaming/merging this package pycharm-professional into pycharm. See more:
https://blog.jetbrains.com/pycharm/2025/04/unified-pycharm/ https://gitlab.archlinux.org/archlinux/packaging/packages/pycharm-community-edition/-/issues/8
Yeah, after seeing the discussion in the issue the best is keeping a bungle JRE version here, I'm preparing the package to rename it
I suggested them to use "pycharm-open-source" or "pycharmium".
For this, I still suggest to rename just to "pycharm".
If I understand the gitlab thread correctly, The current pycharm-community-edition package will become/stay a pycharm package build from only the open source code from jetbrains. Does this mean that the pycharm-professional package will stay a binary release so people with a pro subscription can use these features?
I guess potential new names will then be pycharm-oss or just pycharm for the package in extra and pycharm-bin for the binary release in the aur. Because it's not the pro feature that is different from the package in extra but that it is build from the official binary release instead of the official source. You can use the binary release without a pro subscription to get some features the open source build doesn't have.
@XenGi If it builds fine with makepkg you should file an issue with yay.
https://gitlab.archlinux.org/archlinux/packaging/packages/pycharm-community-edition/-/issues/8 tracks the rename of the repository package.
Even after clearing the cache, pycharm fails to build for me with yay:
==> Starting build()...
:: Building Cython speed-ups
Traceback (most recent call last):
File "/home/xengi/.cache/yay/pycharm-professional/src/pycharm-2025.1/./plugins/python-ce/helpers/pydev/setup_cython.py", line 16, in <module>
from setuptools import setup
ModuleNotFoundError: No module named 'setuptools'
==> ERROR: A failure occurred in build().
Aborting...
-> error making: pycharm-professional-exit status 4
-> Failed to install the following packages. Manual intervention is required:
pycharm-professional - exit status 4
makedepends=('python-setuptools' 'cython') seems to be fine though.
Builds just fine with makepkg and pkgctl build.
I'm agree with having a single package called "pycharm," but where? I just emailed the maintainers of "pycharm-community-edition" to see how best to proceed. While I wait for their response, I've just updated this with the current name. I'll keep you posted on any updates.
@nonZero Yeah, I agree. Needs renaming to just "pycharm". The question is, will not this name wanted to be used by the official package "pycharm-community-edition" from [extra]?
Pinned Comments