[GRASS-dev] Windows - Bug in dll

Hi!

Now, here comes my second problem (ref. "Windows - Bug in path handling" for the first one). System: Windows 7 Prof. 64 Bit, german.

I removed GRASS GIS and reinstalled it to "c:\GRASS_GIS", a destination path without spaces to overcome my first problem. Then the startup goes one step further and stops again. Here is the output:

¦ Cleaning up temporary files...
¦ Starting GRASS GIS...
¦ Traceback (most recent call last):
¦ File "C:\GRASS_GIS\gui\wxpython\gis_set.py", line 32, in <module>
¦ from core.utils import _
¦ File "C:\GRASS_GIS\gui\wxpython\core\utils.py", line 25, in <module>
¦ from grass.script import task as gtask
¦ File "C:\GRASS_GIS\etc\python\grass\script\task.py", line 35, in
¦ <module>
¦ from xml.parsers import expat # TODO: works for any Python?
¦ File "C:\PYTHON26\LIB\xml\parsers\expat.py", line 4, in <module>
¦ from pyexpat import *
¦ ImportError: DLL load failed: %1 ist keine zulõssige Win32-Anwendung.
¦ FEHLER: Error in GUI startup. See messages above (if any) and if
¦ necessary, please report this error to the GRASS developers.
¦ On systems with package manager, make sure you have the right GUI
¦ package, probably named grass-gui, installed.
¦ To run GRASS GIS in text mode use the -text flag.
¦ Use '--help' for further options
¦ grass72 --help
¦ See also: https://grass.osgeo.org/grass72/manuals/helptext.html

The german part of the output means:
  ImportError: DLL load failed: %1 is not a valid Win32 applicatian

I tried both - GRASS GIS 32 Bit as well as the 64 bit variant. Neither of them works.

Any ideas on how to proceed?

Regards,

Mark

C:\GRASS_GIS\etc\python\grass\script\task.py", line 35, in
¦ <module>

AFAIU you're using winGRASS standalone installer. Correct? Which Version?

winGRASS standalone bundles its own python version.

¦ from xml.parsers import expat # TODO: works for any Python?
¦ File "C:\PYTHON26\LIB\xml\parsers\expat.py", line 4, in <module>
¦ from pyexpat import *
¦ ImportError: DLL load failed: %1 ist keine zulõssige Win32->Anwendung.

here it seems to point to an external python living in C:\PYTHON26.

Have you more python version installed on your Windows System?

these several python installations may interfere.

Could you rename C:\PYTHON26 to e.g. C:\xxxxPYTHON26 and try to restart
winGRASS and post the results here?

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Windows-Bug-in-dll-tp5322538p5322540.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Am 31.05.2017 um 21:34 schrieb Helmut Kudrnovsky:
>> C:\GRASS_GIS\etc\python\grass\script\task.py", line 35, in
>> ¦ <module>
>
> AFAIU you're using winGRASS standalone installer. Correct? Which Version?

Yes. V7.2.1.

> winGRASS standalone bundles its own python version.
>
>> ¦ from xml.parsers import expat # TODO: works for any Python?
>> ¦ File "C:\PYTHON26\LIB\xml\parsers\expat.py", line 4, in <module>
>> ¦ from pyexpat import *
>> ¦ ImportError: DLL load failed: %1 ist keine zulõssige Win32->Anwendung.
>
> here it seems to point to an external python living in C:\PYTHON26.
>
> Have you more python version installed on your Windows System?
>
> these several python installations may interfere.

Helmut, you are great!

I was not aware of this old Python installation any more (presumable a left-over from an old Blender setup). Removing it solved both problems I had. :slight_smile:

However, I may install a new blender in near future. As far as I know, it still comes with a separate Python installation.

Any idea on how to avoid such interferences in the future?

Regards,

Mark

However, I may install a new blender in near future. As far as I know,
it still comes with a separate Python installation.

Any idea on how to avoid such interferences in the future?

no idea how blender handles its python installation.

AFAICT I have also a separate python installed and there is no interference
between the winGRASS-bundled python and the separately installed python.

AFAIU it's a matter whether blender adds its python systemwidely to %PATH%
or not.

HTH

-----
best regards
Helmut
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Windows-Bug-in-dll-tp5322538p5322682.html
Sent from the Grass - Dev mailing list archive at Nabble.com.

Am 01.06.2017 um 17:30 schrieb Helmut Kudrnovsky:

However, I may install a new blender in near future. As far as I know,
it still comes with a separate Python installation.

Any idea on how to avoid such interferences in the future?

no idea how blender handles its python installation.

AFAICT I have also a separate python installed and there is no interference
between the winGRASS-bundled python and the separately installed python.

AFAIU it's a matter whether blender adds its python systemwidely to %PATH%
or not.

OK, I will keep this in mind and check for it. Thanx!

Mark