<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 01/18/2015 03:26 AM, Martin Dobias wrote:<br>
<blockquote
cite="mid:CAC2XbFfrY=QUFraKST2-t_tH3nU318mGVHJTcitS_amuY64K_g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jan 18, 2015 at 3:59 AM,
Nathan Woodrow <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:madmanwoo@gmail.com"
target="_blank">madmanwoo@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<p dir="ltr">We have a import hook in place so it would be
possible to have just import PyQt and handle which
version is imported on our side however this is a bit
magic and I'm not sure many people would like it. Stuff
like this also breaks tooling because there is no PyQt
module so most auto complete will not work. (I have
tried this trick before to strip Qgs from the front of
all classes on the fly)</p>
</blockquote>
<div><br>
</div>
<div>Agreed that adding magic to import PyQt4 or PyQt5 would
not make things better. Plugin developers still would need
to be aware of that and couldn't use new functionality
from Qt5 anyway. QGIS 3 will supposedly introduce API
cleanup, so the plugins will need to be adjusted anyway
(some more, some less).</div>
</div>
</div>
</div>
</blockquote>
<br>
That would not prevent devs from importing PyQt4 or PyQt5. It will
only offer the possibility to write portable code. If somebody does
not want this he can go ahead and directly import PyQt5 and use all
the new features.<br>
</body>
</html>