[GH-ISSUE #850] Set up async scaffolding YTMusicAsync #517

Open
opened 2026-02-27 23:01:14 +03:00 by kerem · 6 comments
Owner

Originally created by @ahmedmani on GitHub (Jan 16, 2026).
Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/850

Is your feature request related to a problem? Please describe.
The api does not provide any async client which is a pain when using this library in an async code base.

Describe the solution you'd like
An Async client that can be imported and used in parallel to the regular client.

Is there any intentions on rewriting the code base in async? if not would such addition be wanted in the library? thanks.

Originally created by @ahmedmani on GitHub (Jan 16, 2026). Original GitHub issue: https://github.com/sigma67/ytmusicapi/issues/850 **Is your feature request related to a problem? Please describe.** The api does not provide any async client which is a pain when using this library in an async code base. **Describe the solution you'd like** An Async client that can be imported and used in parallel to the regular client. Is there any intentions on rewriting the code base in async? if not would such addition be wanted in the library? thanks.
Author
Owner

@sgvictorino commented on GitHub (Jan 16, 2026):

See #325

<!-- gh-comment-id:3757796169 --> @sgvictorino commented on GitHub (Jan 16, 2026): See #325
Author
Owner

@sigma67 commented on GitHub (Jan 16, 2026):

An Async client that can be imported and used in parallel to the regular client.

Yes, this is the implementation I am open to and have previously expressed support for: https://github.com/sigma67/ytmusicapi/discussions/846#discussioncomment-15484728

@kaneryu has expressed interest in this as well. Let's keep this issue for tracking the effort and assignee.

@sgvictorino since the request keeps coming I am now open to adding a separately importable, non-breaking async client, despite previously rejecting it.

<!-- gh-comment-id:3758896615 --> @sigma67 commented on GitHub (Jan 16, 2026): > An Async client that can be imported and used in parallel to the regular client. Yes, this is the implementation I am open to and have previously expressed support for: https://github.com/sigma67/ytmusicapi/discussions/846#discussioncomment-15484728 @kaneryu has expressed interest in this as well. Let's keep this issue for tracking the effort and assignee. @sgvictorino since the request keeps coming I am now open to adding a separately importable, non-breaking async client, despite previously rejecting it.
Author
Owner

@sigma67 commented on GitHub (Jan 16, 2026):

I suspect that due to the effort involved we'd need to create multiple separate issues with manageable size to avoid one huge PR.

<!-- gh-comment-id:3758901517 --> @sigma67 commented on GitHub (Jan 16, 2026): I suspect that due to the effort involved we'd need to create multiple separate issues with manageable size to avoid one huge PR.
Author
Owner

@ahmedmani commented on GitHub (Jan 16, 2026):

one way to evade a huge pull request is to setup the async boilerplate with all the methods that would need to be rewritten defined and raise a Not implemented exception. this makes it easier to collaborate and clearly defines what work needs to be done as well as break the conversion into manageable PRs

<!-- gh-comment-id:3760976534 --> @ahmedmani commented on GitHub (Jan 16, 2026): one way to evade a huge pull request is to setup the async boilerplate with all the methods that would need to be rewritten defined and raise a Not implemented exception. this makes it easier to collaborate and clearly defines what work needs to be done as well as break the conversion into manageable PRs
Author
Owner

@sigma67 commented on GitHub (Jan 17, 2026):

For sure, that sounds like a good plan

<!-- gh-comment-id:3764194590 --> @sigma67 commented on GitHub (Jan 17, 2026): For sure, that sounds like a good plan
Author
Owner

@sigma67 commented on GitHub (Feb 5, 2026):

I have renamed the title to reflect this initial step

<!-- gh-comment-id:3851732701 --> @sigma67 commented on GitHub (Feb 5, 2026): I have renamed the title to reflect this initial step
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ytmusicapi#517
No description provided.