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

Go PySide2 🚀 #94

Closed
1 of 3 tasks
lipkau opened this issue Aug 29, 2016 · 9 comments
Closed
1 of 3 tasks

Go PySide2 🚀 #94

lipkau opened this issue Aug 29, 2016 · 9 comments

Comments

@lipkau
Copy link
Collaborator

lipkau commented Aug 29, 2016

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

  • Update to PySide 2
  • migrte to Tkinter
  • migrate to PyGObject
@ewerybody
Copy link
Owner

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.)

@ewerybody
Copy link
Owner

What is Tkinter? And what's PyGObject? Why would that be an option?

@lipkau
Copy link
Collaborator Author

lipkau commented Aug 29, 2016

edited.
better? ;-)

they are GUI libraries.

I believe pip install six would make .items() work in 2.7 --> but I did not test it

@ewerybody
Copy link
Owner

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!

@lipkau
Copy link
Collaborator Author

lipkau commented Aug 29, 2016

so deciding how to solve this was easy.
I am reading about PySide 2. I am very curiouse about how much of it is already working.

at least Qt got involved in the porting this year. things are going much faster

@ewerybody
Copy link
Owner

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.

@ewerybody
Copy link
Owner

ewerybody commented Feb 14, 2018

this fredrikaverpil/pyside2-wheels#69 is also crucial!

@ewerybody ewerybody reopened this Feb 14, 2018
@ewerybody ewerybody changed the title Support of Python < 3.5 Go PySide2 🚀 Jun 13, 2018
@ewerybody
Copy link
Owner

@ewerybody
Copy link
Owner

Alright! I created a branch to test all this, wrote a converter script and it finally popped up already 😃
There are some things breaking still but its not far I guess.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants