and here the link... thx Matthias
[1]
http://spyder-ide.blogspot.ch/2011/06/pyqt-api-1-pyqt-api-2-and-pyside.html
On 05/01/2013 05:34 PM, Matthias Kuhn wrote:
Ciao Marco,
Bin ich unfähig oder hast du den Link vergessen?
Gruss,
Matthias
On Die 30 Apr 2013 18:24:44 CEST, Marco Bernasocchi wrote:
On 04/30/2013 04:01 PM, Matthias Kuhn wrote:
It was not my intent to encourage the postponement of these features to
a later release.
I wanted to get a decision about inclusion or non-inclusion which is
not based on time-constraints of the developers, but instead is
strategic decision.
I think i'd be good to break all _now_ if possible but maybe we can
have some sort of compatibility layer like here [1]?
In my opinion, it can shed a bad light onto the project and discourage
developers from maintaining their plugins if they've got to rework the
whole plugin with several subsequent major releases.
definetly
If this is a top-priority goal for 2.0 I don't mind having it excepted
from the API freeze (and therefore rendering the API freeze pretty much
useless) for a week or two.
Concerning Python 3: This is a mail from 2010 which states, that there
is the possibility to support Python 2 and Python 3 at the same time:
http://lists.osgeo.org/pipermail/qgis-developer/2010-January/008803.html
If this is really possible, I don't see any problems with postponing
the Python 3 update, as we'll be able to have a painless grace period.
yes, I think python 3 can wait, PyQt api 2 mkes the code not only
python3 compatible, but also much simpler.
ciao
Thank you for your feedback
Matthias
--
Marco Bernasocchi
http://opengis.ch
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer
