-
Notifications
You must be signed in to change notification settings - Fork 122
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
simplify HWI install instructions #1317
Comments
That's a great suggestion. I would like to add that in newer versions of Linux (e.g. Ubuntu 23.04 or later but other distros will likely have this issue as well) this doesn't work due to PEP 668. By the way this issue arises with both your suggestion and the original install instructions. So to incorporate both your improvement and a workaround for newer versions of Linux, I'd suggest the following:
|
Interesting, not heard of pipx. So does it automatically create a separate virtualenv for each package installed? Also, does the |
Yeah, pipx is made specifically for application installation. It automatically creates a virtual environment, installs the package, and adds the package's associated applications (entry points) to a location on your PATH.
No, it does not. I just tested it. |
I'd suggest replacing
taproot-assets/docs/external-group-key-ledger.md
Lines 32 to 41 in ac2961a
with
This will then install to
without leaving a residual clone of the repository lying around.
Also, if
~/.local/bin
is in your path (most systems it is, but you might have to log out and back in if pip just created~/.local/bin
so that it will be picked up because it isn't added to the PATH if it doesn't exist when you log in) , the following commands can be simplified from$ ./hwi.py
to
$ hwi
.
The text was updated successfully, but these errors were encountered: