[Bug 17093] console not being connected to stdin/stdout correctly

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=17093

--- Comment #4 from Austin English <austinenglish at gmail.com> 2010-09-08 12:35:45 CDT ---
(In reply to comment #3)
> (In reply to comment #2)
> > I have a feeling that Eric's recent console work may have fixed this. Can you
> > retest in git and/or give clear steps of how to reproduce the problem?
> 
> unfortunately it's quite a bit of work to cut out the relevant buggy portions
> of python, so you'd need to just install python 2.5.2 under wine (which does
> work!) and then fire up "wine python.exe" from an xterm ( making sure that it's
> fired up in a new command.com window )
> 
> what will happen is that the "python >>>" prompt will appear *ON THE XTERM
> OUTPUT*
> 
> when you run python under standard win32, what happens is that you simply do
> not see the "python >>>" prompt until you press return a couple of times.
> 
> this is a bug which has been fixed for python 2.6 and so it is the fact that it
> is a known bug in python 2.5 which is hitting a known bug in win32 _and_ wine
> that is causing the problem.
> 
> l.

In wine-1.3.2-77-gec382f4, if I run:
$ wine python.exe
the '>>>' prompt shows up on the xterm, and I can interact with it there.
If I run
$ wine start python.exe
the '>>>' prompt shows up in its own command.com window, and NOT on the xterm.
I can interact with it there. The '>>>' shows up immediately, and does not
require pressing return for it to appear.

I'm not sure if it's fixed or not, based on your description.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.