<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi<br>
<br>
<div class="moz-cite-prefix">On 09/05/16 10:51, Denis Rouzaud wrote:<br>
</div>
<blockquote cite="mid:57304FA3.8000408@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<font size="-1"><font face="Verdana">Dear all, <br>
<br>
I am raising this again....<br>
<br>
Now that we can build QGIS with Qt5, Python 3, PyQt5, an open
question remains: how do plugins will handle with this?<br>
Starting a QGIS built with PyQt5 using enabled plugins will
probably report a lot of Python crashes.<br>
<br>
</font></font><font size="-1"><font face="Verdana"><font
size="-1"><font face="Verdana">Right now, there is an option
to port plugins when building QGIS.<br>
This solution is fine at the moment although it requires a
rebuild every time you install a new plugin.<br>
</font></font></font></font></blockquote>
This only ports core plugins, so this does not help at all with 3rd
party plugins.<br>
<blockquote cite="mid:57304FA3.8000408@gmail.com" type="cite"><font
size="-1"><font face="Verdana"><font size="-1"><font
face="Verdana"> <br>
But later on, whenever QGIS 3 arises, it would be perfect
to offer a way to plugins to support both 2.x and 3.x, or
not?<br>
</font></font></font></font></blockquote>
<blockquote cite="mid:57304FA3.8000408@gmail.com" type="cite"><font
size="-1"><font face="Verdana"><font size="-1"><font
face="Verdana"> <br>
</font></font>I believe plugins should tell if they handle
python2/pyqt4 or python3/pyqt5 or both (probably using
qgis.PyQt package).<br>
If we choose this path, it should be included in next QGIS
release.<br>
I started a PR on this topic [0] but it only propose to the
plugin to say if they support Python3/PyQt5 and assumes that
it can support only one. This would need to be updated so
plugins could support both.<br>
</font></font></blockquote>
<br>
I would like to see flags for<br>
<br>
py2pyqt4<br>
py3pyqt5<br>
py3pyqt5-experimental<br>
<br>
The last one will allow plugin authors to start porting and receive
user feedback while not yet promoting their plugin as stable under
this version.<br>
<br>
Normally a dev should manually run scripts/2to3 on his plugin, fix
remaining issues and flag as compatible (or experimental if he wants
broader testing first).<br>
<br>
<blockquote cite="mid:57304FA3.8000408@gmail.com" type="cite"><font
size="-1"><font face="Verdana"> What do you think?<br>
Should we stick to the port-plugins and offer nothing else? <br>
</font></font></blockquote>
Nope :)<br>
<blockquote cite="mid:57304FA3.8000408@gmail.com" type="cite"><font
size="-1"><font face="Verdana"> <br>
Cheers,<br>
<br>
Denis<br>
<br>
</font></font></blockquote>
<font size="-1"><font face="Verdana">Matthias</font></font><br>
<blockquote cite="mid:57304FA3.8000408@gmail.com" type="cite"><font
size="-1"><font face="Verdana"> <br>
<br>
<br>
[0] <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/qgis/QGIS/pull/2911">https://github.com/qgis/QGIS/pull/2911</a><br>
<br>
<br>
</font></font> <br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>