Search Criteria
Package Details: python-youtube-transcript-api 1.0.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/python-youtube-transcript-api.git (read-only, click to copy) |
|---|---|
| Package Base: | python-youtube-transcript-api |
| Description: | A Python API which allows you to get the transcripts/subtitles for a given YouTube video. |
| Upstream URL: | https://github.com/jdepoix/youtube-transcript-api |
| Licenses: | MIT |
| Submitter: | jsh6789 |
| Maintainer: | jsh6789 |
| Last Packager: | jsh6789 |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2024-07-30 06:29 (UTC) |
| Last Updated: | 2025-05-16 17:54 (UTC) |
Dependencies (6)
- python-defusedxml (python-defusedxml-gitAUR)
- python-requests
- python-build (make)
- python-installer (make)
- python-poetry-core (python-poetry-core-gitAUR) (make)
- python-wheel (make)
Latest Comments
mistersmee commented on 2025-05-13 17:43 (UTC) (edited on 2025-05-13 17:55 (UTC) by mistersmee)
@jsh6789, I maintain one of the dependents of this package,
open-webui-no-venv, and upstream has moved to 1.0.3, which as of now is the latest version ofyoutube-transcript-api.I checked
python-markitdown, and they also have moved to ~=1.0.0.The only one I'm unsure of if they've moved to 1.0.0 and above is alpaca-ai and alpaca-git.
imo, I think this package can get a package version bump
Also, if alpaca-ai or any other dependent hasn't moved yet, upstream mentioned in the upstream 1.0.0 release notes that: "You'll find more details on the updated API in the README. The old static methods can still be used, but have been deprecated and will be removed in a future version!" https://github.com/jdepoix/youtube-transcript-api/releases/tag/v1.0.0 So, the code in dependents won't immediately break if you bump the package version, the old APIs are still working, but will be removed in a future version.
jsh6789 commented on 2025-03-12 22:15 (UTC)
Version 1.0 has some major API changes that I'm pretty sure will break all software using this package, if I were to update immediately.
Leaving this at the current version for now. If dependents' code starts pulling and using 1.0 then I think that will be the time to update PKGBUILD (or split package).