[Qgis-developer] Release schedule discussion - again

[Nathan Woodrow]

Hey Tom,

I suspect it won't be that bad overall but we do need to just see what is
needed first.  The Python 2 -> 3 change isn't so bad, there is a few things
but they are workable.

The change to PyQt5 is also workable.  You could do this kind of thing for
the imports:

if version >= 3.0:
   from PyQt5.QtCore import *
else:
   from PyQt4.QtCore import *

There is also some other things we could do here to help I think like:

from qgis.PyQt import *

Where qgis.PyQt is a wrapper module around the above version checks so you
don't have to version check in each class.

Changes to the Qt API is the other thing to handle as things have been
removed from Qt4 in Qt5 but I'm not sure on the list.

All in all I don't suspect you will have to maintain two different code
bases just aware of the API differences.  This is mainly what I mean when I
say planning.  Having some resources for people to use

- Nathan

On Wed, Oct 14, 2015 at 10:52 PM, Tom Chadwin <tom.chadwin at nnpa.org.uk>
wrote:

> As the developer of a single plugin, and a very inexperienced one, can I
> ask
> how Py3/Qt5 will work? Will we require separate branches for QGIS2 and
> QGIS3
> versions of our plugins? In other words, it is plausibly feasible to have a
> single plugin codebase which will try Py3/Qt5 and fail back gracefully to
> Py2/Qt4?
>
> I'm guessing not.
>
>
>
> --
> View this message in context:
> http://osgeo-org.1560.x6.nabble.com/Release-schedule-discussion-again-tp5229448p5230089.html
> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20151014/1adc095a/attachment-0001.html>