Rich Healey <ri...@psych0tik.net> added the comment: I have an apology to make for wasting your time.
Further investigation demonstrates that it was evidently fiddling with the Application Verifier that broke everything (although I installed it during my debugging attempts- I'm guessing that something else in VS has the same capabilities). By disabling all tests the application runs, by reenabling them it stops again. I now have a few questions 1) How can the verifier add the flags to the loading mechanism to add the breaks? In that when I installed different versions/clean reinstall of the same version it was still broken. Clearly it doesn't patch the binary, but leaves a flag somewhere (???) about the binary? 2) OK by the looks of it I only had one question ;) thanks for all your help! ---------- status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7206> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
