Message8245

Author zyasoft
Recipients cdleonard, jeff.allen, zyasoft
Date 2014-03-04.16:36:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAL9RhrVmANscgLvVqdRuP0qDjS920mXxTioH6XbnBkOAjcnLYA@mail.gmail.com>
In-reply-to <1393924327.39.0.475450079109.issue2089@psf.upfronthosting.co.za>
Content
sys is problematic in Python, or at least the Jython implementation, given
its unique role - we always seems to be special casing for it. This is just
one more example - we want better console support and we need specific
Closer support.

At least it should be an easy fix.

On Tue, Mar 4, 2014 at 2:12 AM, Jeff Allen <report@bugs.jython.org> wrote:

>
> Jeff Allen added the comment:
>
> I confirm this behaviour. Choosing not to have the fancy console is the
> work-around:
>
> >dist\bin\jython -Dpython.console= -c "import sys;
> sys.stdout.write('hello')"
> hello
> >
>
> I'm pretty sure I broke this. The wrapper I made for the fancy console
> keeps each unterminated output line, defeating the upstream flush() until
> you start a read. This is the only way I found to get the line editing
> JLineConsole to know about the prompt.
>
> As Jim comments, what's needed here is to give my clever wrapper a Closer
> that will flush the "prompt" you never used.
>
> ----------
> assignee:  -> jeff.allen
> keywords: +console
> nosy: +jeff.allen
>
> _______________________________________
> Jython tracker <report@bugs.jython.org>
> <http://bugs.jython.org/issue2089>
> _______________________________________
>
>
Files
File name Uploaded
unnamed zyasoft, 2014-03-04.16:36:53
History
Date User Action Args
2014-03-04 16:36:54zyasoftsetrecipients: + zyasoft, jeff.allen, cdleonard
2014-03-04 16:36:54zyasoftlinkissue2089 messages
2014-03-04 16:36:54zyasoftcreate