Bug report #9323
QGIS Processing Options python error on windows8
|Affected QGIS version:||2.0.1||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||worksforme|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||17930|
Hello, im a forestry student from Portugal, that started working now with a company and used ArcGIS and IDRISI as SIGs. First of all i'd like to thank you for making this software and congratulate you on the great looks you managed to achieve.
I started trying to work with QGIS for a few days now and even though I manage to import shapefiles and calculate areas, that's all i can do. At the start i though it was a plugin issue and starting searching for similar issues but had no luck.
That said i have 2 questions I hope that you can help me:
1) Everytime I open the processing options and click OK to validate anything (even the base options one) i get a error that looks like this [IMG]http://i40.tinypic.com/1628nig.png[/IMG] (i will update a file with the text if anyone wants).
I have no clue about why it is happening, i still have ArcGIS 10.1 and IDRISI Selva installed maybe making the python versions collapse?
2) This one may be correlated and if it is answered anywhere else please direct me to it but i can't seem to find stuff like SEXTANTE and plugins that i see everywhere to download from QGIS, do i have to do it manually or is there a issue with me version? And in case i have to do it manually how do i do it?
Thanks in advance and have a good day
#1 Updated by Richard Duivenvoorde over 7 years ago
- Category set to 94
- Assignee set to Victor Olaya
the main issue is that the python code of processing is not handling utf8 correctly (as seen from the error in your screendump).
Not sure what at that moment is the value that is creating the error. It could be a property of your data (containing non ascii chars), it could be your name 'José' is part of the path where QGIS places the python plugins (and processing plugin). The python code is casting to str (ascii string) which is not possible for the non ascii chars.
So the python code of processing/sextante is to be updated. I'll assign this issue to Victor.