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
qtpy.__version__ should be QtPy version, not Qt version #41
Conversation
Yep I agree as well, I think it was @SylvainCorlay who did the initial packaging and used the |
Nop, I don't think @SylvainCorlay is to be blamed here. I think this is something we inherited from Since @goanpeca is +1, please go ahead with this @astrofrog. I agree with the constants you proposed:
|
👍 too ! |
…QT_VERSION, PYSIDE_VERSION, and QT_VERSION
Code attached - note that for now, I actually went with:
I could easily split |
I'm not sure what convention you want to use for the |
What did you do to transform the initial issue into a PR ? I didn't know that it was possible. |
✨ Magic ✨ Actually I just used the |
Once this is merged, then from my point of view we're good for a 1.1 release from the point of view of glue (all our tests pass). |
Only one of |
@Nodd - oops, of course, sorry about that |
@@ -52,6 +52,9 @@ | |||
|
|||
import os | |||
|
|||
# Version of QtPy | |||
__version__ = "1.1.dev0" |
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.
__version__
is defined here:
https://github.com/spyder-ide/qtpy/blob/master/qtpy/_version.py#L2
Please use that here instead :-)
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.
Done!
Just one minor comment, after that we can merge and release 1.1 |
@ccordoba12 - this should be ready to go |
@ccordoba12 I merged, you can do the release ! |
I think I need to do first a PR in Spyder because of this change. I'll let you know about it :-) |
I think that
__version__
should be set to the actual QtPy version, otherwise packages won't be able to easily check for example that QtPy is recent enough to include certain patches. I think we could then make the Qt and other versions available via e.g.I'd be happy to include a quick PR to include in QtPy 1.1 if others agree?
Of course, we could have
qtpy.QTPY_VERSION
be the QtPy version, but I think it would be counter-intuitive for__version__
to not be that.