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.

Sign up for GitHub

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

Jump to bottom

Use qtpy instead of custom compatibility code #477

Open
nicoddemus opened this issue Feb 1, 2023 · 2 comments · May be fixed by #478
Open

Use qtpy instead of custom compatibility code #477

nicoddemus opened this issue Feb 1, 2023 · 2 comments · May be fixed by #478

Comments

@nicoddemus
Copy link
Member

nicoddemus commented Feb 1, 2023 •
edited

They support type hints, I would suggest to migrate to qtpy, I can help if you want

Originally posted by @nrbnlulu in #474 (comment)
@nicoddemus nicoddemus mentioned this issue Feb 1, 2023
Open
@nicoddemus
Copy link
Member Author

One thing that needs to be supported is selecting backends via environment variables and configuration options.

@nrbnlulu
Copy link

nrbnlulu commented Feb 1, 2023

should be pretty simple qtpy itself uses env var to determine the API

@nrbnlulu nrbnlulu linked a pull request Feb 1, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

migrate to qtpy nrbnlulu/pytest-qt
2 participants
@nicoddemus @nrbnlulu