[PyQt] Question about pyqtlicense tool

[Elvis Stansvik]

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.

Sorry to bring up this old thread again, but we've now gotten our
commercial license.

I've created our commercially licensed wheel by embedding our license
and an LGPL Qt into it using the pyqtlicense, and put that on our own
internal package index server.

However, I would still like to ask again if it's in any way possible
for us to instead use the PyQt wheel straight from PyPI instead, since
that would simplify things.

What is it that the pyqtlicense tool actually does with the license
file? Does it simply copy it into the wheel? Could we do this after
the PyPI wheel was installed, as part of our deployment?

It would simplify things a lot if we didn't have to do this chore of
creating our own specific wheel and having a package index server with
just a single wheel in it, and instead could just use PyPI like we do
with our other deps.

Thanks in advance,
Elvis

>
> Phil