Our code links with msvcr110.dll, but the downloadable python & the extension modules are built using msvcr90. after building python27 with the particular run-times, i attempted -and succeeded- in building a consistent pywin32-219.
I'd like to check my work before tackling py2exe, numpy,& scipy: site-packages\win32\ test, for example, contains testall.py; the comments indicate it should not be run unattended, and Google reveals at least 1 case running "85 tests in 9.719s [...with] FAILED (errors=2)"
what metric do folk use to validate pywin32?
I'd like to check my work before tackling py2exe, numpy,& scipy: site-packages\win32\ test, for example, contains testall.py; the comments indicate it should not be run unattended, and Google reveals at least 1 case running "85 tests in 9.719s [...with] FAILED (errors=2)"
what metric do folk use to validate pywin32?