Re: [Qgis-developer] Processing broken in 2.14?

[Paolo Cavallini]

Il 27/06/2016 10:46, Paolo Cavallini ha scritto:
> Il 27/06/2016 10:30, Jürgen E. Fischer ha scritto:
>> Hi Paolo,
>>
>> On Mon, 27. Jun 2016 at 09:26:49 +0300, Paolo Cavallini wrote:
>>> using repo http://qgis.org/debian-nightly-release Processing is broken
>>> with [0]. Any solution?
>>
>> Should be fixed in fad50ecd [0]
>>
>>
>> Jürgen
>>
>> [0] https://github.com/qgis/QGIS/commit/fad50ecd
> 
> Thanks Jürgen, I'll check with tomorrow package.

Confirmed, fixed.
Thanks.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html



signature.asc
Description: OpenPGP digital signature
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] [Qgis-psc] Redmine -> Github tests

[Nathan Woodrow]

+1 from me also.  Nice work.

On Sat, Jul 2, 2016 at 9:38 AM, Nyall Dawson  wrote:

> On 28 June 2016 at 19:31, Richard Duivenvoorde 
> wrote:
> > Hi Lists (cross posting to have both community, psc and developers),
> >
> > Still busy ways to migrate from Redmine to Github possibilities, we play
> > with some options. Wanted to sent some ideas to the lists of current
> status:
> >
> > Chatting to Matthias (who did a first import script based on Redmine
> > issue.xml imports [0][1]).
> >
> > Chatting to Juergen (who did an import script based on table exports of
> > the Redmine database [2]).
> >
> > Who both hit the Github-api-throtteling limit from Github [3] and
> > stopped there:
> > - max 60 api-search queries per minute
> > - max 5000 requests per hour for other api calls
> >
> > We had a little chat to github support, we were pointed to a different
> > api [4]
> >
> > Receiving python script from Juergen, and his plan to get as much
> > information from Redmine as possible by:
> > - creating a (sqlite) redmine.db with dumps of nessecary tables from
> > (mysql) redmine.db
> > - creating 'lookup'-tables for different mappings, eg map Redmine-users
> > toGithub-users. Have the Category-strings mapped to their id's AND
> > mapped to Github-labels etc etc.
> > - write a python script which queries the db and (via github api)
> > creates issues with exact the same issue-numbers as we have in Redmine
> > - add labels to a Github test repo as 'mapping to Redmine' things like:
> > status, prio, etc etc
> >
> > My conclusion: if I/we invest enough time into this, I can do further
> > scripting and just import the issues in blocks, just enough to not hit
> > the limit.
> >
> > I hand crafted 2 issues:
> >
> > https://github.com/rduivenvoorde/temp/issues/17
> >
> > https://github.com/rduivenvoorde/temp/issues/18
> >
> > based on http://hub.qgis.org/issues/10755
> >
> > To show/see some possible options:
> >
> > - one Redmine comment = one Github comment (as in #17)
> > - all Redmine comments in one Github comment (as in #18)
>
> Another huge +1 in support of your efforts. Fantastic stuff!
>
> My preference would be to the one redmine=one github comment version (#17).
>
> Nyall
>
>
> >
> > You can see all possible labels if you try to create a new issue in the
> > repo:
> > https://github.com/rduivenvoorde/temp/issues
> >
> > I tried to minimize the number of Labels, but tried to mimic most of
> > Redmine's.
> > By adding a number in front of it I hope we can instruct issuers to add
> > for example at least number 1 to 5 labels. And they are ordered by that
> > number in the Github views, making it maybe easier to 'read' them in an
> > apparent order.
> >
> > All imports will be done by a 'QGIS-redmine-import' user.
> > All attributions will be done based on (Redmine) Name and (if available)
> > Github userid (I thin we should leave email addresses away)
> > References to commits and pr's can be mapped.
> > Assignee's can be set on Github userid's
> > Attachment info can be copied (url's to original attachment) BUT(!) the
> > api does not provide a way to add those. This can only be done via
> > Webinterface...
> >
> > The plan is to take a couple of complex issues and fine-tune a script
> > till everybody is satisfied with result.
> >
> > To do this work I need:
> >
> > 1) full backup of community that this is the way to go
> > 2) help / feedback on first tests or coding
> > 3) some time/days? (after 2.16 packaging: 8th july?) to freeze Redmine
> > and dump tables again
> > 4) some encouragement
> >
> > Already done: taking the 4079 users of Redmine, and checked with Github
> > if they have a user with the same email OR userid... Only 321 matched...
> >
> > So also needed (separate threads/emails?):
> > - everybody check this list and see if he/she can match him/herself and
> > sent me his/her right Github id together with the Redmine one
> > - input/comments about current Labels
> > - if we miss something if we do it like this
> >
> >
> > Not sure how to channel this, but thought to sent it like an email
> >
> > Regards,
> >
> > Richard Duivenvoorde
> >
> >
> > [0] https://github.com/m-kuhn/rm2gh
> > [1] https://github.com/m-kuhn/QGIS-Test/issues/
> > [2] https://github.com/jef-n/rm2gh/issues/
> > [3] https://developer.github.com/v3/#rate-limiting
> > [4] https://gist.github.com/jonmagic/5282384165e0f86ef105
> >
> > ___
> > Qgis-psc mailing list
> > qgis-...@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-psc
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: 

Re: [Qgis-developer] [Qgis-psc] Redmine -> Github tests

[Nyall Dawson]

On 28 June 2016 at 19:31, Richard Duivenvoorde  wrote:
> Hi Lists (cross posting to have both community, psc and developers),
>
> Still busy ways to migrate from Redmine to Github possibilities, we play
> with some options. Wanted to sent some ideas to the lists of current status:
>
> Chatting to Matthias (who did a first import script based on Redmine
> issue.xml imports [0][1]).
>
> Chatting to Juergen (who did an import script based on table exports of
> the Redmine database [2]).
>
> Who both hit the Github-api-throtteling limit from Github [3] and
> stopped there:
> - max 60 api-search queries per minute
> - max 5000 requests per hour for other api calls
>
> We had a little chat to github support, we were pointed to a different
> api [4]
>
> Receiving python script from Juergen, and his plan to get as much
> information from Redmine as possible by:
> - creating a (sqlite) redmine.db with dumps of nessecary tables from
> (mysql) redmine.db
> - creating 'lookup'-tables for different mappings, eg map Redmine-users
> toGithub-users. Have the Category-strings mapped to their id's AND
> mapped to Github-labels etc etc.
> - write a python script which queries the db and (via github api)
> creates issues with exact the same issue-numbers as we have in Redmine
> - add labels to a Github test repo as 'mapping to Redmine' things like:
> status, prio, etc etc
>
> My conclusion: if I/we invest enough time into this, I can do further
> scripting and just import the issues in blocks, just enough to not hit
> the limit.
>
> I hand crafted 2 issues:
>
> https://github.com/rduivenvoorde/temp/issues/17
>
> https://github.com/rduivenvoorde/temp/issues/18
>
> based on http://hub.qgis.org/issues/10755
>
> To show/see some possible options:
>
> - one Redmine comment = one Github comment (as in #17)
> - all Redmine comments in one Github comment (as in #18)

Another huge +1 in support of your efforts. Fantastic stuff!

My preference would be to the one redmine=one github comment version (#17).

Nyall


>
> You can see all possible labels if you try to create a new issue in the
> repo:
> https://github.com/rduivenvoorde/temp/issues
>
> I tried to minimize the number of Labels, but tried to mimic most of
> Redmine's.
> By adding a number in front of it I hope we can instruct issuers to add
> for example at least number 1 to 5 labels. And they are ordered by that
> number in the Github views, making it maybe easier to 'read' them in an
> apparent order.
>
> All imports will be done by a 'QGIS-redmine-import' user.
> All attributions will be done based on (Redmine) Name and (if available)
> Github userid (I thin we should leave email addresses away)
> References to commits and pr's can be mapped.
> Assignee's can be set on Github userid's
> Attachment info can be copied (url's to original attachment) BUT(!) the
> api does not provide a way to add those. This can only be done via
> Webinterface...
>
> The plan is to take a couple of complex issues and fine-tune a script
> till everybody is satisfied with result.
>
> To do this work I need:
>
> 1) full backup of community that this is the way to go
> 2) help / feedback on first tests or coding
> 3) some time/days? (after 2.16 packaging: 8th july?) to freeze Redmine
> and dump tables again
> 4) some encouragement
>
> Already done: taking the 4079 users of Redmine, and checked with Github
> if they have a user with the same email OR userid... Only 321 matched...
>
> So also needed (separate threads/emails?):
> - everybody check this list and see if he/she can match him/herself and
> sent me his/her right Github id together with the Redmine one
> - input/comments about current Labels
> - if we miss something if we do it like this
>
>
> Not sure how to channel this, but thought to sent it like an email
>
> Regards,
>
> Richard Duivenvoorde
>
>
> [0] https://github.com/m-kuhn/rm2gh
> [1] https://github.com/m-kuhn/QGIS-Test/issues/
> [2] https://github.com/jef-n/rm2gh/issues/
> [3] https://developer.github.com/v3/#rate-limiting
> [4] https://gist.github.com/jonmagic/5282384165e0f86ef105
>
> ___
> Qgis-psc mailing list
> qgis-...@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-psc
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Sandro Santilli]

On Fri, Jul 01, 2016 at 06:47:16PM +0200, Martin Dobias wrote:

> I think what you are up to is not to find out scale(), but actually
> mapUnitsPerPixel(). Scale in QGIS is calculated as ( extent_width / (
> canvas_width * dpi) ) with some extra conversions involved, see
> QgsScaleCalculator class.

Thanks, with the show() trick, mapUnitsPerPixel() works as expected
(while scale() still gives wild returns, maybe due to wild dpis..)

--strk;
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Martin Dobias]

Hi Tom

On Fri, Jul 1, 2016 at 5:25 PM, Tom Chadwin  wrote:
> Hi Martin
>
>
> Martin Dobias wrote
> iface.mapCanvas().geometry()
>> PyQt4.QtCore.QRect(0, 0, 879, 390)
> iface.mapCanvas().viewport().geometry()
>> PyQt4.QtCore.QRect(3, 3, 873, 384)
>
> Ah, OK! I didn't know anything about a canvas frame. So, without doing
> setFrameStyle(), does canvas.extent() give canvas.geometry() or
> canvas.viewport().geometry()?

With the frame, canvas.extent() is linked to size reported by
cavas.viewport().geometry().

Even better is to use canvas.mapSettings().outputSize() that gives you
the actual image size used for rendering (although it should be the
same as the size from canvas.viewport().geometry()).

Cheers
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Martin Dobias]

Hi Sandro

On Fri, Jul 1, 2016 at 6:07 PM, Sandro Santilli  wrote:
> On Fri, Jul 01, 2016 at 05:58:57PM +0200, Sandro Santilli wrote:
>> On Thu, Jun 30, 2016 at 10:14:34PM +0100, Barry Rowlingson wrote:
>> > Maybe I've missed something here, but doesn't the canvas resize method
>> > set the canvas pixel size? This behaves as expected when run
>> > standalone from a python prompt.
>>
>> It does ! Thanks for the pointer.
>
> Still, my problem is the following:
>
>   QgsMapCanvas *mCanvas = new QgsMapCanvas();
>   mCanvas->resize( QSize(50, 50) );
>   mCanvas->setExtent( QgsRectangle( 0, 0, 50, 50 ) );
>   QCOMPARE( mCanvas->scale(), 1.0 ); //<-- fails, returning 3.1631e+07

I think what you are up to is not to find out scale(), but actually
mapUnitsPerPixel(). Scale in QGIS is calculated as ( extent_width / (
canvas_width * dpi) ) with some extra conversions involved, see
QgsScaleCalculator class.

Try this in PyQGIS console:

>>> cx = QgsMapCanvas()
>>> cx.setFrameStyle(0)
>>> cx.resize(QSize(100,100))
>>> cx.setExtent(QgsRectangle(0,0,100,100))
>>> cx.show()
>>> cx.mapSettings().outputSize()
PyQt4.QtCore.QSize(100, 100)
>>> cx.mapSettings().mapUnitsPerPixel()
1.0

One caveat here is the fact you need to call show() method of canvas,
otherwise the resize event (that sets image output size) will not be
fired and thus the image output size not updated.

Cheers
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [332] geoUmbriaSUIT approval notification.

[noreply]

Plugin geoUmbriaSUIT approval by pcav.
The plugin version "[332] geoUmbriaSUIT 2.6.8" is now approved
Link: http://plugins.qgis.org/plugins/geoUmbriaSUIT/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [412] Qgis2threejs approval notification.

[noreply]

Plugin Qgis2threejs approval by pcav.
The plugin version "[412] Qgis2threejs 1.4.1" is now approved
Link: http://plugins.qgis.org/plugins/Qgis2threejs/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Plugin [1000] Qdraw approval notification.

[noreply]

Plugin Qdraw approval by pcav.
The plugin version "[1000] Qdraw 1.3 Experimental" is now approved
Link: http://plugins.qgis.org/plugins/qdraw/
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Sandro Santilli]

On Fri, Jul 01, 2016 at 05:58:57PM +0200, Sandro Santilli wrote:
> On Thu, Jun 30, 2016 at 10:14:34PM +0100, Barry Rowlingson wrote:
> > Maybe I've missed something here, but doesn't the canvas resize method
> > set the canvas pixel size? This behaves as expected when run
> > standalone from a python prompt.
> 
> It does ! Thanks for the pointer.

Still, my problem is the following:

  QgsMapCanvas *mCanvas = new QgsMapCanvas();
  mCanvas->resize( QSize(50, 50) );
  mCanvas->setExtent( QgsRectangle( 0, 0, 50, 50 ) );
  QCOMPARE( mCanvas->scale(), 1.0 ); //<-- fails, returning 3.1631e+07

--strk;
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] exporting QgsMapToolNodeTool, for testing

[Sandro Santilli]

Attempts to add a test for QgsMapToolNodeTool result
in failures due to the class not being exported.

Is there a policy about what to do in these cases ?
Should I just export the class or is there some other
test-oriented trick ?

--strk; 

  ()   Free GIS & Flash consultant/developer
  /\   https://strk.kbt.io/services.html
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Sandro Santilli]

On Thu, Jun 30, 2016 at 10:14:34PM +0100, Barry Rowlingson wrote:
> Maybe I've missed something here, but doesn't the canvas resize method
> set the canvas pixel size? This behaves as expected when run
> standalone from a python prompt.

It does ! Thanks for the pointer.

--strk;
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Tom Chadwin]

Hi Martin


Martin Dobias wrote
 iface.mapCanvas().geometry()
> PyQt4.QtCore.QRect(0, 0, 879, 390)
 iface.mapCanvas().viewport().geometry()
> PyQt4.QtCore.QRect(3, 3, 873, 384)

Ah, OK! I didn't know anything about a canvas frame. So, without doing
setFrameStyle(), does canvas.extent() give canvas.geometry() or
canvas.viewport().geometry()?

Thanks

Tom



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/setting-QgsMapCanvas-size-for-testing-map-tools-tp5273987p5274394.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Martin Dobias]

Hi Tom!

On Fri, Jul 1, 2016 at 1:08 PM, Tom Chadwin  wrote:
> Barry Rowlingson wrote
>> Maybe I've missed something here, but doesn't the canvas resize method
>> set the canvas pixel size? This behaves as expected when run
>> standalone from a python prompt.
>>
>> from qgis.core import *
>> from qgis.gui import *
>> app = QgsApplication([],True)
>> canvas = QgsMapCanvas()
>> canvas.show()
>> canvas.resize(1000,200)
>> canvas.resize(1000,1000)
>>
>> Note the map canvas has no parent, so just appears on its own at the
>> specified size.
>>
>> Or maybe I've missed a point
>
> I don't want to misrepresent what Sandro is asking, but I think it's the
> same as me. I think (and this is from memory), that we need to do this to
> the QGIS app canvas instance, rather than a newly created one.
>
> When I run canvas.resize() locally, it behaves as I expect. I can then run
> qgis2web (this is my reason for wanting to solve this), to export a web map
> of the same size as the canvas.
>
> What I don't understand is that when testing under Travis, with the same
> canvas.resize() in the test script, I get different bounds in the webmap to
> what I get when resizing my client canvas and exporting.

I guess the problem lies in the fact that canvas widget has a frame at
its edge (it is drawn within the area of canvas widget). There may be
differences between the "internal" area of canvas due to different Qt
styles being used. To see the outer vs inner measurements:

>>> iface.mapCanvas().geometry()
PyQt4.QtCore.QRect(0, 0, 879, 390)
>>> iface.mapCanvas().viewport().geometry()
PyQt4.QtCore.QRect(3, 3, 873, 384)

Probably what you need to do is to remove the frame altogether:

>>> iface.mapCanvas().setFrameStyle(0)

Then you get:

>>> iface.mapCanvas().geometry()
PyQt4.QtCore.QRect(0, 0, 879, 390)
>>> iface.mapCanvas().viewport().geometry()
PyQt4.QtCore.QRect(0, 0, 879, 390)

Hope that helps!

Cheers
Martin
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] setting QgsMapCanvas size, for testing map tools

[Tom Chadwin]

Barry Rowlingson wrote
> Maybe I've missed something here, but doesn't the canvas resize method
> set the canvas pixel size? This behaves as expected when run
> standalone from a python prompt.
> 
> from qgis.core import *
> from qgis.gui import *
> app = QgsApplication([],True)
> canvas = QgsMapCanvas()
> canvas.show()
> canvas.resize(1000,200)
> canvas.resize(1000,1000)
> 
> Note the map canvas has no parent, so just appears on its own at the
> specified size.
> 
> Or maybe I've missed a point

I don't want to misrepresent what Sandro is asking, but I think it's the
same as me. I think (and this is from memory), that we need to do this to
the QGIS app canvas instance, rather than a newly created one.

When I run canvas.resize() locally, it behaves as I expect. I can then run
qgis2web (this is my reason for wanting to solve this), to export a web map
of the same size as the canvas.

What I don't understand is that when testing under Travis, with the same
canvas.resize() in the test script, I get different bounds in the webmap to
what I get when resizing my client canvas and exporting.

This experience was a while ago, of course. Perhaps the qgis2web code has
evolved so that this now works - I'll look into it when I can. However, last
time around, it didn't work for me, hence my earlier message to this list.



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/setting-QgsMapCanvas-size-for-testing-map-tools-tp5273987p5274351.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

[Matthias Kuhn]

On 07/01/2016 12:34 PM, Alessandro Pasotti wrote:
> Thanks!
> 
> I thought that the RefactoringTool: was taking care of that.

I guess you are referring to -DPORT_PLUGINS=ON (which is enabled on
travis/py3).


> Isn't the 2to3 run automatically on the test python files too?

No.
Actually it would be better if it wouldn't even run on plugins, but that
would mean that it would have to be run on their source and that might
potentially break them for python 2. Since plugins miss comprehensive
tests (and most of them miss tests at all) that would point out issues
and since python 2 is our current stable target that's too much risk.
Tests on the other hand have a pretty good test coverage inherently, so
they can be ported statically.

Matthias
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Compiling QGIS debian rules test time out

[matteo]

Hi Matthias,

I see that in debian/rules webkit is disabled for some distribution

ifneq (,$(findstring $(DISTRIBUTION),"sid stretch xenial"))
CMAKE_OPTS += -DWITH_QTWEBKIT=FALSE


I'm on xenial right now.. but same thing happens on a debian stretch 
machine..


anyway it should be installed.. do I have to add also other packages?


matteo@matteo-computer:~/lavori/QGIS/QGIS$ aptitude search webkit | grep 
libqt
i   libqt5webkit5   - Web content engine library for Qt 

p   libqt5webkit5:i386  - Web content engine library for Qt 

p   libqt5webkit5-dbg   - Web content engine library for Qt 
- debugg
p   libqt5webkit5-dbg:i386  - Web content engine library for Qt 
- debugg
p   libqt5webkit5-dev   - Web content engine library for Qt 
- develo
p   libqt5webkit5-dev:i386  - Web content engine library for Qt 
- develo
p   libqt5webkit5-qmlwebkitplugin   - transitional dummy package for Qt 
WebKit Q
p   libqtscript4-webkit - QtScript bindings for the Qt 4 
WebKit libr
p   libqtscript4-webkit:i386- QtScript bindings for the Qt 4 
WebKit libr
p   libqtwebkit-dev - Web content engine library for Qt 
- develo
p   libqtwebkit-dev:i386- Web content engine library for Qt 
- develo
p   libqtwebkit-qmlwebkitplugin - Qt WebKit QML plugin 

p   libqtwebkit-qmlwebkitplugin:i38 - Qt WebKit QML plugin 

i A libqtwebkit4- Web content engine library for Qt 

p   libqtwebkit4:i386   - Web content engine library for Qt 

p   libqtwebkit4-dbg- Web content engine library for Qt 
- debugg
p   libqtwebkit4-dbg:i386   - Web content engine library for Qt 
- debugg





Thanks Matthias!

Matteo
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

[Alessandro Pasotti]

Thanks!

I thought that the RefactoringTool: was taking care of that.

Isn't the 2to3 run automatically on the test python files too?

In my case the error was not directly in a test but in a file imported by a
test: offlineditingtestbase.py is that the reason why it was not refactored?



2016-07-01 12:15 GMT+02:00 Matthias Kuhn :

> Hi Alessandro
>
>
> On 07/01/2016 11:59 AM, Alessandro Pasotti wrote:
> > Hi,
> >
> > I'm trying to adapt a test to Py3/Qt5 and I get this odd error:
> >
> > AttributeError: 'QgsFeatureIterator' object has no attribute 'next'
>
>
> ./scripts/2to3
>
> is your friend
>
> http://stackoverflow.com/a/12274637/2319028
>
> Matthias
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer




-- 
Alessandro Pasotti
w3:   www.itopen.it
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Compiling QGIS debian rules test time out

[Matthias Kuhn]

Hi Matteo,

Is webkit installed?

Matthias

On 07/01/2016 12:26 PM, matteo wrote:
> Hi devs,
> 
> I'm compiling QGIS master on a Ubuntu 16.04 machine (fresh installation)
> with the debian rules..
> 
> after the make running there are some test made, some of them reaches
> the timeout (1500 sec).. is that behavior normal? in this way it takes a
> a huge time to compile QGIS.. is it possible to reduce the timeout size?
> or is that my fault?
> 
> "incriminated" tests are:
> 
>  24/242 Test  #24: qgis_composermultiframetest .***Timeout
> 1500.04 sec
> 157/242 Test #157: PyQgsComposerHtml ...***Timeout
> 1500.09 sec
> 
> 
> 
> Thanks!
> 
> Matteo
> 
> ___
> Qgis-developer mailing list
> Qgis-developer@lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Compiling QGIS debian rules test time out

[matteo]

Hi devs,

I'm compiling QGIS master on a Ubuntu 16.04 machine (fresh installation) 
with the debian rules..


after the make running there are some test made, some of them reaches 
the timeout (1500 sec).. is that behavior normal? in this way it takes a 
a huge time to compile QGIS.. is it possible to reduce the timeout size? 
or is that my fault?


"incriminated" tests are:

 24/242 Test  #24: qgis_composermultiframetest .***Timeout 
1500.04 sec
157/242 Test #157: PyQgsComposerHtml ...***Timeout 
1500.09 sec




Thanks!

Matteo

___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

Re: [Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

[Matthias Kuhn]

Hi Alessandro


On 07/01/2016 11:59 AM, Alessandro Pasotti wrote:
> Hi,
> 
> I'm trying to adapt a test to Py3/Qt5 and I get this odd error:
> 
> AttributeError: 'QgsFeatureIterator' object has no attribute 'next'


./scripts/2to3

is your friend

http://stackoverflow.com/a/12274637/2319028

Matthias
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer

[Qgis-developer] Missing next() method in Python 3 QgsFeatureIterator in master

[Alessandro Pasotti]

Hi,

I'm trying to adapt a test to Py3/Qt5 and I get this odd error:

AttributeError: 'QgsFeatureIterator' object has no attribute 'next'

The C++-like call works fine:

fit=layer.dataProvider().getFeatures(request)
f=QgsFeature()
fit.nextFeature(f)
True


the layer is a test layer:
layer.dataProvider().dataSourceUri()
"dbname='/tmp/tmp57y5_gmm/offlineDbFile.sqlite'
table='wfs_test_point20160701113316894'(Geometry) sql="

Same error in python console with a shapefile layer.

Any idea?


-- 
Alessandro Pasotti
w3:   www.itopen.it
___
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer