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 b
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-
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
Ma
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.dataProvi
