As I understand all terminal commands goes via AppImage
❯ python -m
Argument expected for the -m option
usage: /opt/cursor.AppImage [option] ... [-c cmd | -m mod | file | -] [arg] ...
Try `python -h' for more information.
And this is causing strange bugs! For example venv creation:
python -m venv .venv
❯ cd .venv
❯ tree
.
├── bin
│ ├── activate
│ ├── activate.csh
│ ├── activate.fish
│ ├── Activate.ps1
│ ├── cursor.AppImage -> /opt/cursor.AppImage
│ ├── python -> cursor.AppImage
│ ├── python3 -> cursor.AppImage
│ └── python3.11 -> cursor.AppImage
├── include
│ └── python3.11
├── lib
│ └── python3.11
│ └── site-packages
├── lib64 -> lib
└── pyvenv.cfg
You can see it create cursor.AppImage and symlinks python → cursor.AppImage
This is totally incorrect venv structure, it cant work as venv in this way. But if I create venv in same way from Linux Terminal - all works as usual, python and pip files created, no cursor apps inside.