[PyQt] A Heads Up for PyQt Packagers

[Phil Thompson]

On 20 Jun 2018, at 10:21 pm, Scott Kitterman <debian at kitterman.com> wrote:
> 
> On Wednesday, June 20, 2018 10:08:35 PM Phil Thompson wrote:
>> On 20 Jun 2018, at 5:35 pm, Dmitry Shachnev <mitya57 at ubuntu.com> wrote:
>>> Hi Phil, and thanks for the heads up!
>>> 
>>> On Sun, Jun 17, 2018 at 10:27:54PM +0100, Phil Thompson wrote:
>>>> This will mainly be of interest to people who create sip, PyQt4, PyQt5
>>>> etc.
>>>> packages for Linux but also anybody who builds from source.
>>>> 
>>>> Starting with v5.11 (ie. the next release) PyQt5 will use a private copy
>>>> of
>>>> the sip module. Packagers have the choice of including it with PyQt5 or
>>>> creating a new package (PyQt5_sip?). The wheels will use the second
>>>> approach (because the module is Python version specific, whereas the
>>>> PyQt5 modules themselves are not).
>>> 
>>> What about “official” PyQt5 addons (such as QScintilla or PyQt3D), and
>>> third-party PyQt5 addons — will they use standalone sip, or sip from
>>> PyQt5?
>> 
>> They will all use the private copy.
>> 
>>> Will the standalone sip be updated, or 4.19.8 will be the last release of
>>> 4.x?
>> The creation of a private copy is just a configuration option for sip. I
>> would expect Linux packages to continue to do exactly the same as before as
>> far as sip is concerned. For PyQt5 the dependency on that sip package
>> should be removed. The choice is then to create a new package containing
>> PyQt5's private copy and make PyQt5 dependent on that - or just to include
>> the private copy in the PyQt5 package itself.
> 
> If we make a package for the 'private copy' can QScintilla2, etc use the same 
> one?

There is no need. The configuration and build of "sub-packages" like that will automatically pick up the private copy.

Phil