QtXml is really, damn slow. PyQt with QtXml is worst then lxml, just to make a comparison. Switching to a streamlined xml parser would be advisable, but I know it would a deep refactoring for a lot of QGIS's code. Maybe it should be considered within the next big refactorings (geometry, composer, etc.), but it won't be easy to find a sponsor specifically for this...
giovanni Il 04/dic/2014 09:45 "Nyall Dawson" <nyall.daw...@gmail.com> ha scritto: > On 4 December 2014 at 19:25, Jürgen E. <j...@norbit.de> wrote: > > Hi Matthias, > > > > On Wed, 03. Dec 2014 at 16:46:11 +0100, Matthias Kuhn wrote: > >> I didn't look at it in detail and just based this recommendation on the > >> one from the QtXml documentation linked at the end of the original > message. > >> Is there something in particular you think we will be missing? If so, it > >> might be good to start looking for alternative ways to go. > > > > We could just keep using it and fork it if need be. Any idea why it was > > discontinued? > > > > This link [1] suggests that it hasn't been discontinued, it's just > unmaintained, and isn't scheduled for removal. That doesn't solve the > PyQt5 problem though... It's also worth noting that QtXml is very > slow, which is noticeable on project load/save. > > > Nyall > > [1] https://bugreports.qt-project.org/browse/QTBUG-32926 > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/qgis-developer