Re: [python-win32] ExportAsFixedFormat's ValueError
Kaweit wrote: i make a question: doc.ExportAsFixedFormat(output, constants.wdExportFormatPDF,|Item||=||constants.wdExportDocumentWithMarkup, CreateBookmarks ||=||constants.wdExportCreateHeadingBookmarks)| but "ValueError",the argument was wrong. Cloud you help me? I think I need a Win32com Docutment. This is not a win32com issue, it is a Word issue. And it would have been easier if you had told us that you were using Word instead of making us guess. We don't know were "ExportAsFixedFormat" comes from. Why didn't you cut-and-paste us the exact error message? Did it tell you which argument was wrong? What, exactly, is "output"? It would be helpful to see the code leading up to this as well. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. smime.p7s Description: S/MIME Cryptographic Signature ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
[python-win32] ExportAsFixedFormat's ValueError
Hello： i make a question: doc.ExportAsFixedFormat(output, constants.wdExportFormatPDF,Item=constants.wdExportDocumentWithMarkup, CreateBookmarks =constants.wdExportCreateHeadingBookmarks) but "ValueError",the argument was wrong. Cloud you help me? I think I need a Win32com Docutment. -- Best regards Kaweit___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
[python-win32] almost there -- running "py -2 setup.py install"
I have been working for a while on writing a script to provision a machine to be able to build pywin32 using downloadable components, the most important of which is the VCforPython27 compiler package. It seems that in packaging that compiler, at least one header file needed to build pywin32 was left out. Here is where my last attempt failed: ... > C:\Users\vagrant\pywin32>py -2 setup.py install > Building pywin32 2.7.224.1 > running install > running build > running build_py > running build_ext > Skipping mapi: The header 'edkmdb.h' can not be located. > Skipping exchange: The header 'edkmdb.h' can not be located. > Skipping exchdapi: No 64-bit library for utility functions available. > building 'win32ui' extension > c:\Program Files (x86)\Common Files\Microsoft\Visual C++ for > Python\9.0\VC\Bin\amd64\cl.exe /c /nologo /Ox /W3 /GS- /DNDEBUG /MD > -DDISTUTILS_BUILD -D_CRT_SECURE_NO_WARNINGS -Icom/win32com/src/include > -Iwin32/src -IC:\Python27\include -IC:\Python27\PC "-IC:\Program Files > (x86)\Windows Kits\8.1\include\um" "-IC:\Program Files (x86)\Windows > Kits\8.1\include\shared" /TpPythonwin/dbgthread.cpp > /Fobuild\temp.win-amd64-2.7\Release\Pythonwin/dbgthread.obj -DBUILD_PYW > -D_AFXDLL -D_AFXEXT -D_MBCS /Zi > /Fdbuild\temp.win-amd64-2.7\Release\win32ui_vc.pdb /EHsc /wd4163 > dbgthread.cpp > c:\users\vagrant\pywin32\pythonwin\stdafx.h(18) : fatal error C1083: > Cannot open include file: 'afxwin.h': No such file or directory > error: command 'c:\\Program Files (x86)\\Common Files\\Microsoft\\Visual > C++ for Python\\9.0\\VC\\Bin\\amd64\\cl.exe' failed with exit status 2 > > The offending file is pythonwin/stdafx.h which calls for several afx*.h files. Can these headers safely be ignored and skipped over, like the edk* ones are? If not, can someone refer me to a suitable source for the definitions? There is a folder with the missing library names in Visual Studio 2017 Build Tools, but I suspect that it would not have the correct values for version 9, would it? -- Vernon Cole ___ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
