[PyQt] Question about pyqtlicense tool

Elvis Stansvik elvstone at gmail.com
Mon Feb 20 10:24:41 GMT 2017

2017-02-20 10:13 GMT+01:00 Phil Thompson <phil at riverbankcomputing.com>:
> On 20 Feb 2017, at 6:22 am, Elvis Stansvik <elvstone at gmail.com> wrote:
>> 2017-02-19 23:10 GMT+01:00 Phil Thompson <phil at riverbankcomputing.com>:
>>> On 19 Feb 2017, at 6:02 pm, Elvis Stansvik <elvstone at gmail.com> wrote:
>>>> The installation docs says:
>>>> "Installing the Commercial Version
>>>> It is not possible to provide wheels for the commercial version in the
>>>> same way they are provided for the GPL version:
>>>> the user’s license information has to be applied
>>>> it is not possble to distribute a copy of the commercial version of Qt.
>>>> [...]"
>>>> I just have to ask: If I want to use PyQt under a commercial license,
>>>> but against LGPL Qt, couldn't the license information be applied
>>>> afterwards, after the wheel has been installed? It would be very
>>>> convenient if I could just pip install PyQt from PyPI, and then apply
>>>> the PyQt license (using some tool similar to pyqtlicense).
>>> Most organisations would license the commercial wheel and pip install it from an internal server.
>> Right, I was just curious if it would be possible to take it from
>> PyPI, and then embed the license into that, as it would make things
>> slightly simpler. We currently do not have a PyPI server. I know it's
>> very simple to set one up, but it would be great if we could install
>> PyQt the same way we do all our other dependencies (we use
>> pip-compile/pip-sync from pip-tools to maintain our requirement.txt
>> files). Is there something that prevents this (install wheel first,
>> license afterwards), provided we're going to use Qt under LGPL?
> Only that it requires extra development.

Alright, thanks for clarifying.


> Phil

More information about the PyQt mailing list