-
Notifications
You must be signed in to change notification settings - Fork 10
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
Go PySide2 🚀 #94
Comments
a2 was never written with Python 2.x! There was a time when it ran but I doubt it actually does now (I make vast use of the items() dictionary iterator which is named iteritems() in 2.x.) |
What is Tkinter? And what's PyGObject? Why would that be an option? |
edited. they are GUI libraries. I believe |
Do you have any idea how much Qt code is in this project? I feel almost insulted for the suggestion to consider another ui lib! It'll be PySide2 and nothing else! |
so deciding how to solve this was easy. at least Qt got involved in the porting this year. things are going much faster |
Yea we are working with Qt5 here already and the guys are building PySide2 freshly to use it. Seems it's actually the current official way to get it. Maybe I can get a build and try a2 on it. Might even be, that there is no change needed to make it run. So the options are:
Currently I don't see any benefit from having 3.5 and no problems using 3.4. "It's not the latest" does not seem crucial at the time. |
this fredrikaverpil/pyside2-wheels#69 is also crucial! |
Alright! I created a branch to test all this, wrote a converter script and it finally popped up already 😃 |
Expected Behavior
I bid to make a2 compatible with Python 3.5 or greater
Current Behavior
a2 only works with Python 3.0 to 3.4
Possible Solution
The text was updated successfully, but these errors were encountered: