Skip to content

[Security] Update to PyQt5 #897

Description

As you know Qt4 is no longer receiving security updates, you should switch to Qt5 and its python bindings.
The switch from pyqt4 to pyqt5 should be relatively easy according to pyqt documentation on this topic (for example here).

Activity

  1. bmng-dev commented on Sep 5, 2016

    @bmng-dev
    Contributor

    It is not so much PyQt but Qt itself that is the issue. Windows XP is still a supported platform for PyBitmessage. However Windows XP (and Vista) is missing from Qt5's Supported Platforms, although Qt for Windows - Specific Issues indicate it might be possible to build Qt5 for Windows XP. I understand @PeterSurda builds Qt4 as part of the release process so it is up to whether he can successfully build Qt5 and ensure everything still works on Windows XP before switching.

  2. ghost changed the title [-]Qt4 is no longer receiving security updates, it is advised to change to Qt5 and PyQt5.[/-] [+][Security] Update to PyQt5[/+] on Nov 25, 2016
  3. bmng-dev commented on Nov 29, 2016

    @bmng-dev
    Contributor

    Sorry @ghost, it's not up to me. I don't know why @PeterSurda hasn't responded.

  4. PeterSurda commented on Nov 29, 2016

    @PeterSurda
    Member

    There are no specific plans, there are higher priority things. I'd prefer code that works both with Qt4 and Qt5 if possible, if someone submits a pull request I'll be happy to look at it.

  5. added this to the Undefined milestone on Nov 29, 2016
  6. Lvl4Sword commented on Jun 28, 2017

    @Lvl4Sword
    Contributor

    @bmng-dev I'm confused as to why XP/Vista would be supported at all, since those are EOL according to Microsoft ( and thus should be updated/replaced )
    I stand by ghost's advice on not standing by these out-of-date systems

  7. bmng-dev commented on Jun 30, 2017

    @bmng-dev
    Contributor

    @Lvl4Sword you and me both. I'm just someone who is interested in Bitmessage like you. I am not, nor have I ever been, involved in the decision making process of this project. At the time I responded to @ghost I thought Windows XP was supported because of things I had read from @PeterSurda (other issues here on github, on the forums, reddit, or on the bitmessage chan I can't remember) and tried to be helpful with a timely response anticipating what some of @PeterSurda concerns might be about moving to Qt5. The jury is still out on whether I'm correct or not.

  8. PeterSurda commented on Jun 30, 2017

    @PeterSurda
    Member

    Just to clarify:

    • at the moment, the backwards compatibility with Windows doesn't appear to create extra effort. I build the 32bit binaries on Windows 7, and while I do have a test environment for XP, I don't recall having problems since switching the build environment to Windows 7. Today's devel snapshot also works on Windows XP, even though I haven't done any tests on XP since releasing 0.6.2. I haven't really tested most of the post-0.6.2 changes on anything else than linux for that matter. It's possible that at some stage the backwards compatibility will break, and I'll make a decision at that time.

    • the reason why I haven't switched to PyQt5 is that it's lower priority than other things. I don't know what the differences between Qt4 and Qt5 are and I'm not a UI specialist.

  9. a17r commented on Feb 15, 2018

    @a17r

    Please note that Qt4 and PyQt4 support is being dropped in distributions everywhere at this point, since being unmaintained for years.

  10. PeterSurda commented on Feb 15, 2018

    @PeterSurda
    Member

    Sadly, I'm busy with more urgent issues and I've never used PyQt5 before. Maybe someone else can do that. @g1itch any interest?

  11. g1itch commented on Feb 15, 2018

    @g1itch
    Collaborator

    Actually I started already. And have first preview.

  12. 93 remaining items

  13. self-assigned this
    on Jun 29, 2021
  14. added a commit that references this issue on Jul 4, 2021
    f7fdbdf
  15. added a commit that references this issue on Jul 13, 2021
    9c4a323
  16. added 7 commits that reference this issue on Aug 19, 2021
    41b1f39
    7769198
    5796490
    cb67d5a
    f9411a9
    ce57aee
    dbe9345
  17. added a commit that references this issue on Oct 7, 2021
    d2aae68
  18. added a commit that references this issue on Nov 6, 2021
    1c71059
  19. added a commit that references this issue on Nov 26, 2021
    9641279
  20. added 2 commits that reference this issue on Dec 13, 2021
    eedd93e
    c39c7d1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions