Help installing Autokey on openSUSE

[realoik]

Hi there! I’m relatively new to Linux and openSUSE so please bear with me a little

I’m having a problem installing Autokey, at least the latest version (0.96, listed here: https://github.com/autokey/autokey).

Per the github page (https://github.com/autokey/autokey/wiki/Installing#dependencies), it’s supposed to be installed with pip3 and I am having trouble getting that working on Tumbleweed. I’m running Python 3.13.11 and whenever I try running the pip3 install command I get the output:

localhost:~ # pip3 install autokey
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try
    zypper install python313-xyz, where xyz is the package
    you are trying to install.
    
    If you wish to install a non-rpm packaged Python package,
    create a virtual environment using python3.13 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip.
    
    If you wish to install a non-rpm packaged Python application,
    it may be easiest to use `pipx install xyz`, which will manage a
    virtual environment for you. Install pipx via `zypper install python313-pipx` .

note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.

Using the command as the terminal suggests gives me the standard Package not found message.

localhost:~ # zypper install python313-autokey
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Package 'python313-autokey' not found.
Resolving package dependencies...
Nothing to do.
localhost:~ # 

I am not sure if I am using that command wrong, or if I am missing a repo and could use some advice.

[hendersj]

Not all python packages get built as packages - there are an awful lot of them. But not letting pip potentially stomp on system packages is a good thing, because it doesn’t leave your system in an inconsistent (and difficult-to-diagnose) state.

But that’s why the message says ‘try this’ - because if a system package does exist, you can install it that way.

If not, there’s a second option presented in the message - to use a virtual environment. That’s generally a preferred way to handle something like this, and it’s easy to do and manage, and no system packages get stomped on because the venv is set up in the user’s space (and you can have multiple venvs - usually best practice is one per application or project).

[malcolmlewis]

Hi, there is a test build you can download (I don’t publish) and test. It still needs a cleanup, but if you can confirm it’s working to your requirements I may push to Factory.
Test Package ;
https://build.opensuse.org/package/show/home:malcolmlewis:TESTING/python-autokey

Download (You have to log in to download);
https://build.opensuse.org/projects/home:malcolmlewis:TESTING/packages/python-autokey/repositories/openSUSE_Tumbleweed/binaries

[malcolmlewis]

I see it’s X based The gtk version I could test as it runs, the qt version requires Plasma stuff which I don’t use.

[realoik]

This ended up doing it, thank you!
It gave me an error about not having a public key but ignoring it let the install go through and I can launch the application now
I will keep poking at it over the weekend and see if it is stable but for now I am marking this as solved. Thank you for the help!