http://bugs.winehq.org/show_bug.cgi?id=16968
--- Comment #8 from Luke Kenneth Casson Leighton lkcl@lkcl.net 2013-03-04 18:37:48 CST --- no, because it's a very specific and quite obscure bug.
actually, there's a bug in python 2.5 which shows that there is a corresponding bug in wine, and this is the best repro case to show it.
if you use python 2.6, the bug in python 2.6 is fixed (correct initialisation of stdin / stdout during python 2.6 startup) and the problem DOES NOT occur.
it is only when stdin / stdout is incorrectly initialised - as is done in python 2.5 - that the bug in wine occurs, i.e. the stdin/stdout gets sent to the xterm in which wine was started up rather than dropping it on the floor.
if you install python 2.5 under w32, and run "python.exe" from CMD.EXE, you will find that you have to press <return> a couple of times in order to get it to wake up. once this "hiccup" is correctly duplicated under wine, then you will know that you have the problem correctly fixed.