| 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: | 292 |
| Popularity: | 0.51 |
| First Submitted: | 2013-09-25 03:56 (UTC) |
| Last Updated: | 2025-03-20 13:26 (UTC) |
i try this steps and pycharm works fine with me till now:
charm script from /usr/bin/charm.pycharm.desktop -> pycharm.desktop any charm rename it to pycharmsudo ln -s /opt/pycharm/bin/pycharm.sh /usr/local/bin/pycharm. check this: https://www.jetbrains.com/help/pycharm/working-with-the-ide-features-from-command-line.html#cdce0ebdi hope this help.
Is it possible to commit the 2023.1 changes to a branch so that those who want to test it out can clone and run the build themselves? I have tried testing it out myself and I agree there are still some UI bugs. I also don't know what to do about the warning I'm getting: "Obsolete launcher script found." If you have a solution to the last problem @Xavier, I'd be interested to know what that is.
There is not only the issue I reported, there are some others bugs and regressions related to the new release. IMHO I use this IDE on a daily basis so I prefer stability, the best thing here is to wait at least for the first patch. @zappaboy can do it manually but this release requires other adjustments in the pkgbuild
@zappaboy, you can if you can't to wait (:
Anyone can update to "pkgver=2022.3.3" to "pkgver=2023.1" ?
Thank you for the maintenance. Here is the issue to track.
Hi folks, I am going to delay the update to the new version for a bit, I tested and personally the migration dialog fails to me, after that it seems to work well but I need to be sure, I'm going to wait for the response of the issue in the tracking bugs.
I also encountered the error with invalid shasum. I simply deleted the cache directory of package build and the upgrade finished successfully:
rm -fr /var/tmp/pamac-build-${USER}/pycharm-professional && pamac update
@guiastro (update) then your downloaded file is corrupted, download it again
Pinned Comments