Skip to content
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

Integrate Python 3.7 or Above right into the QMPlay Appimage hence no Older Python problem #851

Closed
leirbag28 opened this issue Jan 8, 2025 · 3 comments
Labels

Comments

@leirbag28
Copy link

As someone who has Python 3.6 and will not/can not upgrade it or risk damaging my other Python apps, I have seen it is possible to integrate Python 3.10 into the Appimage making it even more Universal and requiring less from the outside. I downloaded CHIRP.Appimage which is software for configuring HAM/GMRS Walkie Talkie Radios (https://github.com/goldstar611/chirp-appimage/releases/tag/20250103). They just Added Python 3.10 to their latest edition and it seems to work!.

So as a Feature Request so that YouTube works Universally for everyone even if they don't have python 3.7 or above, this would be great to implement!

@zaps166
Copy link
Owner

zaps166 commented Jan 15, 2025

Is it possible to use custom path for yt-dlp in QMPlay2 with https://github.com/niess/python-appimage ?

@zaps166
Copy link
Owner

zaps166 commented Jan 16, 2025

Is it possible to use custom path for yt-dlp in QMPlay2 with https://github.com/niess/python-appimage ?

Tested, it works (need script to launch yt-dlp using this AppImage, use this script as custom path in QMPlay2).


Better way:

  1. Download yt-dlp_linux from https://github.com/yt-dlp/yt-dlp/releases
  2. Set it as custom yt-dlp path in QMPlay2 settings (General Settings page, scroll down)
  3. Uncheck "Don't auto-update" to allow auto-updates of yt-dlp.
  4. Apply and enjoy.

@zaps166 zaps166 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2025
@leirbag28
Copy link
Author

leirbag28 commented Jan 17, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants