[Qgis-developer] [processing] OGR imports full of "None" strings, lately

[Sandro Santilli]

I've noticed lots of "None" strings in the ogr2ogr call from master_2
branch onward and it looks like what you get from unicode(None) in
python.

The code checks for parameter values's length being > 0 before adding
params to ogr2ogr call but all the empty param are now real "None"
strings (due to unicode call).

This doesn't seem happen in 2.16 branch.

Victor: something to mass-clean ?

--strk;