-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pipx #103
base: main
Are you sure you want to change the base?
Pipx #103
Conversation
Thanks for the PR, I'm not sure what to make of this as we already have Can you check if your changes can be integrated into |
Thanks for the PR review! asfik, the major difference is that
Reasons to favor
Simply, I just think installing |
Could you move the |
Hello, I've looked for a solution to install I have also updated a bit about the Cheers! |
Update on the situation: https://www.youtube.com/watch?v=35PQrzG0rG4 |
@kohane27 If pipx is not supported, is it better to install vosx in a venv so that it does not clutter the package list? |
Hello @ideasman42 , hope you're doing well. Thank you for creating
nerd-dictation
. I'm actually using it right now as I write (speak) this paragraph!The need for
pyproject.toml
I'm on archlinux and I encountered the following problems:
pip3 install vosk
:vosk-api
requires Java 17 to build, which I don't have, and think it's an overkillxdotool
but I'm on WaylandSolution
This PR is a continuation of #60. afaik, it's now favored to use
pyproject.toml
as a standard way of specifying project metadata, which could be used by pipx. So this PR includes a simplepyproject.toml
. Then, users can just install the program with a simple command:Thank you!