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

Merge branch 'v0.6' into qt5-wip #2237

Open
wants to merge 38 commits into
base: v0.6
Choose a base branch
from

Conversation

kashikoibumi
Copy link

I have merged the branch 'v0.6' into 'qt5-wip' in 'Porting bitmessageqt to Qt5 #1389' by @g1itch .

It seems work well in Python2.7 + Qt.py + PyQt5.
But, it seems not work with PyQt4.
I will continue investigating this issue.

QtPy is a compatibility layer which allows to use the code written for
PyQt5 with any python Qt binding: PyQt4, PyQt5, pyside or pyside2.

Main differences in PyQt5:

  - all widget classes are now in QtWidgets package, not QtGui;
  - QString obsoleted by unicode (sip API 2);
  - changed the way of signals connection.

Closes: Bitmessage#1191
customwidgets in ui-files and QtGui.QPen instantiation
  - added Qt API string into support request
  - finished flake8 formatting
(for simple encoding like for extended)
resolved pylint redefined-variable-type warnings,
marked autogenerated modules for skipping by pylint and flake8
on tabs "Send", "Blacklist" and "Network Status":
in qt5 it's probably true by default.
@kashikoibumi
Copy link
Author

In order to run with both PyQt4 and PyQt5, Qt.py (qtpy) should be used directly without using the fallback 'PyQt5', although Qt.py becomes a must-dependency.
It seems OK, so I'm going on.

@kashikoibumi
Copy link
Author

Now PyBitmessage runs with either of PyQt5 or PyQt4 by using Qt.py.

But, does not pass the tests.py ..
I have no idea for this currently.

@kashikoibumi
Copy link
Author

I also tried to run with PySide2, but failed with some errors.
It may be sufficient to be runnable with PyQt5 and PyQt4, so I don't seek a path with PySide2 now.

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

Successfully merging this pull request may close these issues.

None yet

2 participants