[PyQt] Experimental PyQt5 v5.6 Wheels Available
Baz Walter
bazwal at ftml.net
Sun Apr 10 18:58:35 BST 2016
On 10/04/16 18:24, Phil Thompson wrote:
> On 10 Apr 2016, at 6:08 pm, Baz Walter <bazwal at ftml.net> wrote:
>>
>> On 10/04/16 09:34, Phil Thompson wrote:
>>> On 9 Apr 2016, at 10:05 pm, Baz Walter <bazwal at ftml.net> wrote:
>>>>
>>>> It definitely seems that some variant of (2) + tool is to be
>>>> preferred. One immediate issue I noticed is that things like style
>>>> plugins need to be copied to the bundled Qt installation in order
>>>> to get full equivalence with a normal system installation. Not
>>>> exactly a big deal, but there's no need to worry about little
>>>> details like that if it's possible to target an existing Qt
>>>> installation.
>>>
>>> Which plugins are missing?
>>
>> I use the qtcurve style plugin, which is quite widely used. I also use a custom platform-theme plugin, and there are desktops like LXQt/LXDE which have something similar. But more generally, I'm just referring to any third-party plugins that the user might have installed as part of their normal setup. From what you said earlier, it seems like there's no way for the wheel to discover such plugins at runtime, right?
>
> Correct. When I was talking about providing a tool I was thinking about something that would point the PyQt modules to the Qt installation - which would pick up those plugins.
>
> However on Windows you couldn't do that (at least it's beyond my current Windows skills) and would instead have to copy in the sub-set of Qt to the location that the PyQt modules have been built to expect. (That's actually how I create the wheels at the moment.) That would pick up those plugins as well (assuming they had been installed with the rest of Qt).
>
>>>> But what exactly is the main purpose of these wheels? Are they
>>>> primarily aimed at users who just need to run PyQt applications?
>>>
>>> Developers of PyQt applications as well - but not people who need to
>>> develop additional wrappers based on PyQt.
>>
>> Okay, so then what about developer tools like Qt Creator/Designer, etc? Wouldn't it still be necessary to have a second Qt installed to get a full dev environment?
>
> Yes, but I don't see a problem with that. I actually see benefits - if you are stuck with developing against an older version of Qt you can still use the latest tools.
>
> Phil
>
--
Regards
Baz Walter
More information about the PyQt
mailing list