To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95028 Issue #|95028 Summary|python.exe does not call WSAStartup Component|udk Version|OOO300m9 Platform|PC URL| OS/Version|Windows, all Status|NEW Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P3 Subcomponent|code Assigned to|sb Reported by|sb
------- Additional comments from [EMAIL PROTECTED] Thu Oct 16 15:48:48 +0000 2008 ------- This is discussed at <http://udk.openoffice.org/servlets/ReadMsg?list=dev&msgNo=4146> ("However, when..."), with a workaround ("import socket") presented at <http://udk.openoffice.org/servlets/ReadMsg?list=dev&msgNo=4147>. See also issue 95024. The correct solution would be to let pyuno/zipcore/python.cxx:1.4 implement SAL_IMPLEMENT_MAIN_WITH_ARGS instead of plain main/wmain, so that sal/osl/w32/salinit.cxx:1.3 sal_detail_initialize is called at startup (which calls WSAStartup). However, that would need further rework, as brand-layer python.exe does not find URE-layer sal3.dll (rather, python.exe expands the PATH so that subsequent programs do find it). --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
