Here is what I have tried to install Python under wine so far following what is recommended in http://wiki.jswindle.com/index.php/Wine_MSI. This was done using wine-1.3.8 with WINEDEBUG set to nothing (i.e., "WINEDEBUG=") so that all warning/error messages would be output.
wine@raven> wine msiexec /i python-2.7.1.amd64.msi fixme:storage:create_storagefile Storage share mode not implemented. fixme:advapi:LookupAccountNameW (null) L"wine" (nil) 0x32f130 (nil) 0x32f134 0x32f128 - stub fixme:advapi:LookupAccountNameW (null) L"wine" 0x179f10 0x32f130 0x176bf8 0x32f134 0x32f128 - stub
The lack of err: messages is encouraging. In particular notice these results have no
err:msi:call_script Could not find CLSID for Windows Script
which seemed to be an issue for another wine user that has attempted this with prior wine versions.
So I had some hope that the above command actually worked, but it returned very quickly with no other response than above, and "find -name python.exe found nothing created by it in the whole wine account area I have set up to deal with wine matters. Thus, I don't think it worked.
Is there some clue in the above fixme messages that indicates something fatal happened with msiexec?
Is there anything else I should be doing? Another thread about a prior unsuccessful attempt to install Python under wine had this quote:
"I have downloaded http://www.dll-files.com/dllindex/dll-files.shtml?msvcirt and placed it in the .wine/drive_c/windows/system directory."
I don't have a clue about the significance of that step since I have no Windows experience and little wine experience. Is that step important or is it no longer necessary with wine-1.3.8? Anyhow, my test above was without that step since I didn't understand its necessity/significance.
To give you some background about my use case, my development environment has been exclusively Linux since 1996, and I have no Microsoft Windows experience at all. Nevertheless, I help with developing the PLplot package which works on all of Linux, Mac OS X, and Windows so I try to help out the PLplot Windows developers by attempting to build PLplot under wine to follow/confirm what they do and any errors they find. As part of that work, I would like to test the optional PLplot Python bindings under wine which motivates my interest in installing the Windows version of Python under wine.
Any help with the proper procedure for installing Python under wine would be much appreciated.
Alan __________________________ Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________
Linux-powered Science __________________________
On Mon, Dec 6, 2010 at 1:19 PM, Alan W. Irwin irwin@beluga.phys.uvic.ca wrote:
Here is what I have tried to install Python under wine so far following what is recommended in http://wiki.jswindle.com/index.php/Wine_MSI. This was done using wine-1.3.8 with WINEDEBUG set to nothing (i.e., "WINEDEBUG=") so that all warning/error messages would be output.
wine@raven> wine msiexec /i python-2.7.1.amd64.msi
Try the 32-bit version instead.
Though wine-devel is for development communications, not general help. Use wine-users for assistance.