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

Migrate from pyobjc to a ctypes based backend on macOS? #24

Open
samschott opened this issue Jul 12, 2021 · 1 comment
Open

Migrate from pyobjc to a ctypes based backend on macOS? #24

samschott opened this issue Jul 12, 2021 · 1 comment

Comments

@samschott
Copy link

I have just stumbled upon this project and it is exactly what I have been looking for / thinking to implement myself.

However, one minor complication for adopting it on my side is the reliance on pyobjc and extension modules. If you are still maintaining the project, would you be open to migrate to a ctypes-based solution, for example using rubicon-objc? If yes, I'm happy to submit a PR.

@Kentzo
Copy link
Member

Kentzo commented Jul 13, 2021

I know that pyobjc works well, so I'm a bit hesitant to jump onto something else. But I'd happy to switch to python-only solution.

Perhaps you'd start by addition an additional config backend?

@samschott samschott changed the title Migrate from pyobjc to a ctypes base backend on macOS? Migrate from pyobjc to a ctypes based backend on macOS? Jul 17, 2021
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