http://bugs.winehq.org/show_bug.cgi?id=17093
Summary: console not being connected to stdin/stdout correctly Product: Wine Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: lkcl@lkcl.net
under certain circumstances, it's possible for stdin and stdout to become connected, instead of to a command prompt window (e.g. wineconsole cmd.exe) to the linux command xterm that started the command prompt window.
downloading the standard python 2.5.2 executable and running it i confirmed that this situation occurs when msvcrt is set to native _or_ to builtin (but i haven't confirmed with msvcr71 native, which is what python 2.5.2 exe is built with).
the msi for python2.5.2 can be downloaded here: http://www.python.org/ftp/python/2.5.2/python-2.5.2.msi
and the .exe and the dll can be extracted - you will need both python.exe _and_ python25.dll - using cabextract, you _don't_ need to actually install it.
anything on the command line (e.g. python.exe -c 'print "hello"') or python -v -i *change* the way that the code operates and *does* work.
also, redirection works e.g. echo 'print "hello"' | ./python.exe
... but not interactive operation (without explicitly saying so using the -i option).