Package Details: pycharm-professional 2023.2.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
Conflicts: pycharm, pycharm-community-eap, pycharm-community-edition, pycharm-community-jre, pycharm-community-jre-aarch64, pycharm-eap
Provides: pycharm
Submitter: hippojazz
Maintainer: Xavier (37h4n)
Last Packager: Xavier
Votes: 280
Popularity: 2.85
First Submitted: 2013-09-25 03:56 (UTC)
Last Updated: 2023-08-24 18:11 (UTC)

Dependencies (22)

Required by (0)

Sources (4)

Pinned Comments

Latest Comments

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

Xavier commented on 2023-08-23 20:27 (UTC)

@J5lx /opt/pycharm-professional/plugins/python/helpers/pydev/_pydevd_bundle/pydevd_cython.cpython-311-x86_64-linux-gnu.so I didn't do a full test if that is a real problem or no, but I prefer to avoid that wrong path linked. To fix your build issue, just install the makedepends (I need to move it as depends)

J5lx commented on 2023-08-23 08:28 (UTC)

Which binaries specifically? I tried looking around for a bit after rebuilding the package with the build steps moved back to the PKGBUILD, but so far I didn’t see anything that seemed to have problematic absolute paths linked in.

Xavier commented on 2023-08-18 23:45 (UTC)

Hi @j5lx, I had that cython part in the build section of the pkgbuild before, but the issue is that some binaries compiled by cython link the absolute path of the location of the files. To avoid it, I changed the building part of the speed-up when the files are deployed in the final destination using post-script install. If you have a better solution, I'm open to hear ideas.

J5lx commented on 2023-08-18 21:21 (UTC)

This package seems to be missing some dependencies needed by the install script. Since the script seems to perform some kind of build tasks, I think it would be a good idea to move them to the build() function in the PKGBUILD if possible, so those missing dependencies can be declared as build-time rather than run-time dependencies. Or is there a particular reason why those build steps can’t be included in the PKGBUILD?

:: Building Cython speed-ups
Traceback (most recent call last):
  File "/opt/pycharm-professional/plugins/python/helpers/pydev/setup_cython.py", line 16, in <module>
    from setuptools import setup
ModuleNotFoundError: No module named 'setuptools'
/opt/pycharm-professional/plugins/python/helpers/pydev/pydevd_attach_to_process/linux_and_mac /
/tmp/alpm_o3udz0/.INSTALL: line 8: g++: command not found
/
:: Cython speed-ups done

qubidt commented on 2023-07-19 09:17 (UTC)

@jmcb I have the same issue. It seems like a bug in jetbrains' terminal emulator (and its interpretation of xterm- escape codes)? It doesn't always happen consistently either.

A workaround that works for me is to tell less (man's default pager, which I assume you are also using), to not send the termcap initialization strings. This seems (on my system at least) to avoid the triggering whatever condition that causes man to produce an empty screen. i.e., instead of man du, you can run LESS="$LESS --no-init" man du.

You can have your shell automatically use this workaround by setting the environment variable on startup. You can check if you're running inside jetbrains' terminal with the TERMINAL_EMULATOR env variable. e.g. in .bashrc/.zshrc:

if [[ "$TERMINAL_EMULATOR" = JetBrains-JediTerm ]]; then
    export LESS="$LESS --no-init"
fi

jmcb commented on 2023-05-26 21:08 (UTC) (edited on 2023-05-26 21:09 (UTC) by jmcb)

Whenever I try to open a manual page in the integrated terminal, I get nothing but a bunch of tildes, and it says something like: Manual page man(1) byte 0/0 (END) (press h for help or q to quit)

man works fine in any other console. in pycharm this happens with both bash and fish. Does anyone else have this problem? Is this an upstream issue? I can't find any youtrack bug entries on it for some reason, I would have thought it would be pretty important

p.s. less and bat both work fine. man -H also works

Xavier commented on 2023-05-04 02:18 (UTC)

Building locally the speedup debugger is not ready for Python 3.11, I disabled it until it is fixed: issue

arcanis commented on 2023-05-04 00:20 (UTC)

does not compile with python3.11, I guess https://github.com/archlinux/svntogit-community/blob/packages/pycharm-community-edition/trunk/fix-compile-cython-extensions-error.patch has to be added

tocic commented on 2023-04-30 06:47 (UTC)

I have the following warnings with the current HEAD that were not present in 983be5d:

[1/1] Cythonizing _pydevd_bundle/pydevd_cython.pyx
/usr/lib/python3.10/site-packages/Cython/Compiler/Main.py:369: FutureWarning: Cython directive 'language_level' not set, using 2 for now (Py2). This will change in a later release! File: /tmp/makepkg/pycharm-professional/src/pycharm-2023.1.1/plugins/python/helpers/pydev/_pydevd_bundle/pydevd_cython.pxd

==> WARNING: Package contains reference to $srcdir
opt/pycharm-professional/plugins/python/helpers/pydev/_pydevd_bundle/pydevd_cython.cpython-310-x86_64-linux-gnu.so
opt/pycharm-professional/plugins/python/helpers/pydev/_pydevd_frame_eval/pydevd_frame_evaluator_39_310.cpython-310-x86_64-linux-gnu.so

Xavier commented on 2023-04-28 18:30 (UTC)

The first patch was released 2023.1.1, the first startup bug is fixed for the next major release and not for this release and I hope it doesn't have side consequences, but at least several important bugs were fixed in this patch.

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