8000 PyQt license · Issue #300 · mxcube/mxcubeqt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
PyQt license #300
Open
Open
@rhfogh

Description

@rhfogh

As agreed in the last two meetings, we must comply with LGPL license conditions. This means that any group that is developing code that uses PyQt must have a commercial license before the code starts shipping. The cost is 450 Euro (+ VAT) as a one-off payment, for each seat. See https://www.riverbankcomputing.com/commercial/ for details.

GPhL has now bought a license; could the rest of you check whether you 1) never develop Qt-related code? 2) Already have a commercial Qt license? or 3) are going to buy one now?

The operative part of the Riverbank license FAQ is as follows - I gather we are not distributing PyQt, but having the users use their own copy:

Q. | Can my proprietary application be used with the copy of the GPL version of PyQt that the user already has installed (as part of their Linux distribution for example)?

A. | Yes, so long as you meet the following conditions:

    - you are using the LGPL version of Qt

    - your proprietary application has been developed with the commercial version of PyQt

    - your commercial PyQt license covers the version of PyQt that the user has installed.

Q. | Can I distribute my own copy of the GPL version of PyQt with my proprietary application?

A. | Yes, so long as you meet the following conditions:

   - the GPL version of PyQt is packaged and installed separately from your pr
55F9
oprietary application

   - you meet all of the obligations of the GPL regarding your PyQt package

   - you are using the LGPL version of Qt

   - your proprietary application has been developed with the commercial version of PyQt

   - your commercial PyQt license covers the version of PyQt that you are distributing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0