Installer broken (Trac #63)

[cfobel]

Tested on version v0.1-376-gb5170d7, Win7 and XP.

When you run the installed .exe, it produces the following traceback:

Traceback (most recent call last): File "", line 25, in File "C:\pyinstaller\iu.py", line 436, in importHook mod = _self_doimport(nm, ctx, fqname) File "C:\pyinstaller\iu.py", line 521, in doimport exec co in mod.dict File "C:\buildbot\microdrop\WinXP_Py2_7\build\build\pyi.win32\microdrop\outPYZ1.pyz/matplotlib", line 765, in File "C:\buildbot\microdrop\WinXP_Py2_7\build\build\pyi.win32\microdrop\outPYZ1.pyz/matplotlib", line 683, in rc_params File "C:\buildbot\microdrop\WinXP_Py2_7\build\build\pyi.win32\microdrop\outPYZ1.pyz/matplotlib", line 599, in matplotlib_fname File "C:\buildbot\microdrop\WinXP_Py2_7\build\build\pyi.win32\microdrop\outPYZ1.pyz/matplotlib", line 246, in wrapper File "C:\buildbot\microdrop\WinXP_Py2_7\build\build\pyi.win32\microdrop\outPYZ1.pyz/matplotlib", line 520, in _get_data_path_cached File "C:\buildbot\microdrop\WinXP_Py2_7\build\build\pyi.win32\microdrop\outPYZ1.pyz/matplotlib", line 485, in _get_data_path RuntimeError: Path in environment MATPLOTLIBDATA not a directory

Running the .exe from the dist directory seems to work ok, so I suspect that it is a problem with the msi installer.

Migrated from http://microfluidics.utoronto.ca/ticket/63

{
    "status": "closed", 
    "changetime": "2014-04-17T19:39:01", 
    "description": "Tested on version v0.1-376-gb5170d7, Win7 and XP.\n\nWhen you run the installed .exe, it produces the following traceback:\n\nTraceback (most recent call last):\n  File \"<string>\", line 25, in <module>\n  File \"C:\\pyinstaller\\iu.py\", line 436, in importHook\n    mod = _self_doimport(nm, ctx, fqname)\n  File \"C:\\pyinstaller\\iu.py\", line 521, in doimport\n    exec co in mod.__dict__\n  File \"C:\\buildbot\\microdrop\\WinXP_Py2_7\\build\\build\\pyi.win32\\microdrop\\outPYZ1.pyz/matplotlib\", line 765, in <module>\n  File \"C:\\buildbot\\microdrop\\WinXP_Py2_7\\build\\build\\pyi.win32\\microdrop\\outPYZ1.pyz/matplotlib\", line 683, in rc_params\n  File \"C:\\buildbot\\microdrop\\WinXP_Py2_7\\build\\build\\pyi.win32\\microdrop\\outPYZ1.pyz/matplotlib\", line 599, in matplotlib_fname\n  File \"C:\\buildbot\\microdrop\\WinXP_Py2_7\\build\\build\\pyi.win32\\microdrop\\outPYZ1.pyz/matplotlib\", line 246, in wrapper\n  File \"C:\\buildbot\\microdrop\\WinXP_Py2_7\\build\\build\\pyi.win32\\microdrop\\outPYZ1.pyz/matplotlib\", line 520, in _get_data_path_cached\n  File \"C:\\buildbot\\microdrop\\WinXP_Py2_7\\build\\build\\pyi.win32\\microdrop\\outPYZ1.pyz/matplotlib\", line 485, in _get_data_path\nRuntimeError: Path in environment MATPLOTLIBDATA not a directory\n\nRunning the .exe from the dist directory seems to work ok, so I suspect that it is a problem with the msi installer.", 
    "reporter": "ryan", 
    "cc": "", 
    "resolution": "fixed", 
    "_ts": "1397763541728826", 
    "component": "microdrop", 
    "summary": "Installer broken", 
    "priority": "blocker", 
    "keywords": "", 
    "version": "0.1", 
    "time": "2012-03-08T16:27:58", 
    "milestone": "Microdrop 1.0", 
    "owner": "cfobel", 
    "type": "defect"
}

[cfobel]

Trac update at 20120308T16:36:31: ryan commented:

I just realized that the paths listed in the traceback (i.e., "C:\buildbot\microdrop...") are paths from the machine that the .exe was built on. These paths do not exist on the machine trying to run the .exe.

Even if I install an .msi file onto the same machine that created it, I get a similar error, but the paths listed are from the build directory rather than the install directory.