Conversation
Contributor
|
Related: #61218, the same PR but for IntelliJ IDEA. There we just removed the community and professional versions and replaced it with So perhaps it also makes more sense to remove |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a more involved change.
As described in PyCharm blogpost, Pycharm Community Edition and Pycharm Professional Edition were merged into unified PyCharm. Version 2025.1 is the last version of PyCharm Community.
Current
pycharm-communityVoid package fails to build, because its distfile returns 404, so making some change is warranted. I also have a strong suspicion that version 2025.1 is incompatible with the currently packaged version of Python. I've been having issues withpycharm-communitydebugger which seem to be resolved in later versions.The initial version of this PR is nonintrusive. It might make more sense to fully replace the
pycharm-communitypackage in a similar manner as explained in the Manual. But both packages are nonfree, so doing this correctly is not as important as if would be if it the packages were freely available in the repo.I would have pinged the maintainer of
pycharm-communityand offered them maintainership ofpycharm, but Felix Van der Jeugt's GitHub account no longer exists.I cannot make reasonable changes to the
pycharm-communitypackage (like revbumping it and adding an install message imploring the user to switch topycharm) because the distfile is dead.I've added
newer PyCharm bundles a library which provides both aarch64 and arm64 versions.
xbps-srcchokes on that during shlib resolving phase, since it expectsx86_64. The fact that aarch64 libraries are present could imply thatpycharmcould work onaarch64(and not only onx86_64, which is the current limitation)I did very basic testing with my Python project. I can confirm that PyCharm's debugger works now.
This PR coicidentally resolves #48245
Things that should perhaps be done
replace/delete/make a virtual package out of
pycharmfigure out an
updatefileI have verified that
pycharm-community'supdatefile doesn't list many versions past 2025.1. I have therefore removed it when copyingpycharm-communitytopycharm.install message forpycharm-community?Kinda mutually exclusive with the first point. It was implemented, so this is no longer relevant.
Testing the changes