-
-
Notifications
You must be signed in to change notification settings - Fork 153
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
PR: Fix imported modules logic if 'FORCE_QT_API' is empty #230
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This does seem like the intended behavior based on the comment, though I'm not sure why it wasn't caught in the original PR #194 . This will affect backward compatibility. however, but no way around that due to how it was implemented previously.
@JasonGilholme any feedback here?
This comment has been minimized.
This comment has been minimized.
thanks @CAM-Gerlach for taking care of this quite fundamental package. How can i trigger the gh-actions-based checks? |
Hi @CAM-Gerlach any progress on the maintainers issue? looking at #229 #233 #225 and others i feel like many other packages are waiting for qtpy to bump its version, drop qt4 and support pyside6 |
could you please pay a little attention on this base package too? Or delegate work to a new maintainer. |
another month, another reminder @andfoy @ccordoba12 ;) |
Hi @hiaselhans could you remove the unrelated commits from this PR? Or if is better for you, maybe we can help you with that? Let us know :) |
Hi @dalthviz ! great to see some news here… |
Thank you for the fast response @hiaselhans ! I think that now these commits are in the branch so if you create a new PR that uses the same branch will lead still to seeing them. What you could try is to create a new clean branch (using as base an updated master branch version) and then cherry pick the commits here that are actually related to the import logic for |
Ok i think i can do it later today :) |
d724840
to
3f676d9
Compare
hi @dalthviz i removed all commits but that one :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @hiaselhans ! LGTM 👍
As mentioned in #222 i stumbled across this.
before:
after (expected behaviour):
It seems obvious to me and i spare further explination.