[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] PyQt4 Support for Multiple APIs
From:       Scott Kitterman <debian () kitterman ! com>
Date:       2016-01-30 18:31:34
Message-ID: 13344357.nexPSCPUEg () kitterma-e6430
[Download RAW message or body]

On Saturday, January 30, 2016 06:15:46 PM Phil Thompson wrote:
> As you probably know, PyQt4 supports multiple, incompatible APIs...
> 
> http://pyqt.sourceforge.net/Docs/PyQt4/incompatible_apis.html
> 
> The old APIs were the default for Python v2 and the new ones the default for
> Python v3.
> 
> The feature was added to aid in the porting of applications from Python v2
> to Python v3. It was never intended that production code should make use of
> it - although I doubt I ever made that as explicit as I should have. For
> example, all the packages used by an application must agree to use the same
> APIs, which makes using third-party code problematic.
> 
> With hindsight it's something I wish I'd never implemented. The code to
> support it is complex and is unlikely to be used again in the future - so
> it will probably not get tested properly. Consequently I'm considering
> dropping the support in SIP v4.18 and PyQt v4.12.
> 
> Please let me know if you are switching to the later APIs in your Python v2
> code. Hopefully nobody is, but maybe everybody is...

Searching what's in the Debian archive, sip.setapi seems to be quite common 
[1].  Any suggestions on how to narrow that down to the ones that might be 
problematic?

Scott K

[1] https://codesearch.debian.net/perpackage-results/sip.setapi/2/page_0
_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
[prev in list] [next in list] [prev in thread] [next in thread]