[issue19283] Need support to avoid Windows CRT compatibility issue.

Martin v. Löwis added the comment: In any case, this issue has too little information to be able to reproduce it in a meaningful way. Closing as out-of-date. -- resolution: -> out of date status: open -> closed ___ Python tracker

[issue19283] Need support to avoid Windows CRT compatibility issue.

Mark Lawrence added the comment: Is there a specific Python question here? -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bug

[issue19283] Need support to avoid Windows CRT compatibility issue.

Debarshi Goswami added the comment: My question is, even a FILE* of MSVC10 type is provided, why these APIs are crashing, after all it expects MSVC10 type. -- ___ Python tracker ___

[issue19283] Need support to avoid Windows CRT compatibility issue.

Antoine Pitrou added the comment: The easy answer is: don't execute a script, import a module instead (and either do something at that module's top-level, or execute a function inside the module). Also, as for ABI issues, take a look at: http://docs.python.org/3.3/c-api/stable.html --

[issue19283] Need support to avoid Windows CRT compatibility issue.

Debarshi Goswami added the comment: If any workaround is available. It is also fine. -- type: -> crash ___ Python tracker ___ ___ Pyt

[issue19283] Need support to avoid Windows CRT compatibility issue.

New submission from Debarshi Goswami: Some support is needed to avoid compatibility issues in different version of CRT in Windows. I have an application which embeds Python interpreter and the application is build on MSVC11, whereas I am using Python 3.3.2 which is build on MSVC10. I know ther