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

py-win32more would get rid of pycaw.api #96

Open
KubaO opened this issue Sep 10, 2024 · 1 comment
Open

py-win32more would get rid of pycaw.api #96

KubaO opened this issue Sep 10, 2024 · 1 comment

Comments

@KubaO
Copy link

KubaO commented Sep 10, 2024

This is a proposal, not a bug report.

Pycaw.api is a hand-crafted ctypes interface to Windows APIs used in pycaw.

There's a machine-generated projection of Windows API (the whole thing) to Python at https://github.com/ynkdir/py-win32more. Removing Pycaw.api and using win32more as a dependency would get rid of a lot of code that has to be maintained. win32more also has an easy-to-use COM wrapper system, so comtypes also wouldn't be needed. It also interfaces with winrt and cleanly handles winrt inheritance should that be needed for any newer APIs.

py-win32more is self-contained and is pure Python. It has no dependencies besides Python itself.

If this would be of interest, I can follow up with a pull request.


I am not associated with the win32more project, just a very happy user.

@AndreMiras
Copy link
Owner

Thank you for the proposal.
I didn't know about py-win32more, it's an interesting project indeed.
My main concerns are regarding the breaking changes this would introduce and the fact that py-win32more is relatively new (2 years).
But having part of the code generated would be the way to go indeed.
Let's keep that one open in case others want to chime in

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

No branches or pull requests

2 participants