[issue9672] test_xpickle fails on Windows: invokes pythonx.y instead of pythonxy

Georg Brandl added the comment: Closing for reasons Antoine stated. -- nosy: +georg.brandl resolution: -> works for me status: open -> closed ___ Python tracker ___ _

[issue9672] test_xpickle fails on Windows: invokes pythonx.y instead of pythonxy

Antoine Pitrou added the comment: This is not a failure, it just indicates that the tests get skipped. While I agree that ideally the tests should be able to run on all systems, it should also be noted that the pickle protocols are (supposed to be) platform-agnostic and, therefore, it is not m

[issue9672] test_xpickle fails on Windows: invokes pythonx.y instead of pythonxy

Changes by Terry J. Reedy : -- nosy: +alexandre.vassalotti, pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue9672] test_xpickle fails on Windows: invokes pythonx.y instead of pythonxy

Sridhar Ratnakumar added the comment: > On Windows, that should be python24.exe (not python2.4.exe). Hmm, that is only true for ActivePython. For detecting Python interpreters installed on the system, a simple approach could be to hardcode the full paths, as done by tox: http://code.google.co

[issue9672] test_xpickle fails on Windows: invokes pythonx.y instead of pythonxy

New submission from Sridhar Ratnakumar : test_xpickle 'python2.4' is not recognized as an internal or external command, operable program or batch file. 'python2.5' is not recognized as an internal or external command, operable program or batch file. 'python2.6' is not recognized as an internal or