Search Criteria
Package Details: pyradio 0.9.3.11.28-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/pyradio.git (read-only, click to copy) |
|---|---|
| Package Base: | pyradio |
| Description: | Internet radio player for the command line |
| Upstream URL: | https://github.com/coderholic/pyradio |
| Licenses: | MIT |
| Submitter: | sng |
| Maintainer: | sng |
| Last Packager: | sng |
| Votes: | 10 |
| Popularity: | 0.008178 |
| First Submitted: | 2021-08-31 12:16 (UTC) |
| Last Updated: | 2026-03-13 12:07 (UTC) |
Dependencies (17)
- python-charset-normalizer
- python-dateutil (python-dateutil-gitAUR)
- python-dnspython (python-dnspython-gitAUR)
- python-netifaces (python-netifaces-plusAUR)
- python-psutil
- python-requests
- python-rich
- python-build (make)
- python-installer (make)
- python-pip (make)
- python-setuptools (make)
- python-wheel (make)
- mkvtoolnix-cli (optional) – fix mplayer recordings, add chapters to recordings
- mplayer (mplayer-gui-svnAUR) (optional) – as backend
- mpv (mpv-light-pulseAUR, mpv-gitAUR, mpv-build-gitAUR, mpv-full-luajit-gitAUR, libmpv-gitAUR, mpv-fullAUR, mpv-full-gitAUR, mpv-amd-full-gitAUR, mpv-full-build-gitAUR) (optional) – as backend
- python-dbus-next (python-dbus-next-gitAUR) (optional) – required for MPRIS support
- vlc (vlc-noxAUR, vlc-gitAUR) (optional) – as backend
Latest Comments
1 2 Next › Last »
sng commented on 2026-02-02 21:05 (UTC) (edited on 2026-02-02 21:05 (UTC) by sng)
@musqz
This is probably because of the python update 3.13->3.14
I would just reinstall
musqz commented on 2026-02-02 11:03 (UTC)
After today's update I get this error when launching pyradio.
I cannot find the module or how to fix this. Though the git version works.
But I rather use and stay with the mabox repo (same as aur).
sng commented on 2024-12-29 14:47 (UTC)
@blacktav
Yes, I know what you mean, it is frustrating, but I think it is unavoidable. I whish we could have an automated bumping mechanism for such cases, but aur packages are not officially supported, so...
Even manually bumping the package release would not guarantee that the package update would happen after the actual python update (on the user's machine), which makes the whole thing unreliable
blacktav commented on 2024-12-29 13:31 (UTC)
After a recent update, pyradio failed to start because modules could not be found Cause was modules being installed for python3.12 instead of active python3.13
Simple solution is to use "--rebuild" to force rebuilding of the package
Maybe bumping the package release could force this
sng commented on 2024-04-05 14:13 (UTC) (edited on 2024-04-05 14:13 (UTC) by sng)
Yes!
Thank you very much!
Looking forward to your feedback!
m040601 commented on 2024-04-05 14:08 (UTC) (edited on 2024-04-05 14:12 (UTC) by m040601)
@sng
Ahh ... I see now.
Pity he lost interest.
I say, pity, because "pyradio" is still one of the few "complete" text radio clients for Linux.
Especially the "radio-browser api" integration is in my opinion very important.
You should adopt and own the repo then. You are the one to have put so much work in it in the last years.
Yeah, not so "bad" as xdg-utils.
But anyway, I think I'll better first compile and organize my thoughts and suggestions.
And I will later then go to the github repo (issues) itself and leave the feedback there. It's more appropriate.
sng commented on 2024-04-05 13:52 (UTC)
@m040601
I think that having ttf-dejavu as a dependency is not such a big problem, or is it?
I would be perfectly happy to remove it too
sng commented on 2024-04-05 13:49 (UTC)
@m040601 I am the current developer but I am not coderholic, the guy who started this project back in '11, but then lost interest in it
I just kind of "adopted" the repo back in '18 after submitting some PRs
Yes, this is what explains it...
And you are right, I just did not check for extra dependencies...
I will have a look into xdg-open alternatives
m040601 commented on 2024-04-05 13:41 (UTC) (edited on 2024-04-05 13:56 (UTC) by m040601)
@sng
Thanks for the reply.
Ohh ???!!! So you are the "coderholic" guy also ? https://github.com/coderholic/pyradio
Nice. Thank you for the tool.
In the meantime I did my self some checking and found in the repo "docs/packaging.md":
So that seems to explain it ???
Any way. It would be nice if as core principle "pyradio" did not make any assumptions of what the user is running. Don assume a graphical desktop, a window manager, not even starting X/Wayland.
I see this a lot lately in many other tools mandatory imposing special fonts with cute icons, smileys and patches. Totally unnecessary.
Here is my personal opinion:
Keep it simple and bloat free. Always consider carefully if any thing should be optional or mandatory. Or have a fallback.
Dont break conventions or standards. Key bindings, default pagers, workflows etc.
People who like pyradio are terminal/text lovers. They want it simple and concise. Doing one thing well. Integrating nicely with other text tools if possible. They are already used to and have some "conventions" in their head (emacs, vim, or whatever). They dont want to relearn and have to memorize new paradigms/interfaces.
For those others who like it flashy and graphical. If they wanted a graphical radio browser with lotz of bells, whistles, flash colors, pictures, buttons they would be installing a graphical one to use with the mouse or gestures.
Thanks in advance.
1 2 Next › Last »