Re: [Jython-dev] Switching away from jline back to old InteractiveConsole.

[Philip J. <pj...@un...>]

On Tue, Feb 26, 2013 at 5:50 PM, fwi...@gm... <
fwi...@gm...> wrote:

> On Tue, Feb 26, 2013 at 4:10 PM, Alan Kennedy <jyt...@xh...>
> wrote:
> > [Frank]
> >
> >> Yeah, sadly it seems like the right thing to do. Even more sadly I'm
> >> sure we will get a bunch of bug reports since 2.5 will suddenly cease
> >> working the way people expect. If we want this in for 2.5.4 we need to
> >> do it fast, I'm getting ready to do an RC2. We could leave it to 2.5.5
> >> otherwise.
> >
> > One alternative is that we put some form of warning that
> >
> > A: jline is in use
> > B: Has presented some problems
> > C: How to switch to a different console
> >
> > Just a thought?
> >
> > I think it's an important issue that is frustrating for a lot of users.
> >
> > A much larger group of users than the more technically oriented group
> that
> > would complain if the fancier facilities of jline were not available.
> Also,
> > the latter group would be more likely to go poking in the registry file
> to
> > change things around.
> I think you where right the first time, we should definitely switch to
> the old console until we are certain that JLine works well on all
> common platforms and leave the registry as the place to switch. I'll
> put a note in the release about how to get JLine back.
>
> I think you asked to have the issue assigned to you (or was that
> something else....?), if so do you know how quickly you can switch it?
> I can wait a few days for RC2 to allow for the change.


Thanks for categorizing all of these, Alan

A few of these issues marked (the 2 high priority ones too) don't seem
JConsole related, though:

http://bugs.jython.org/issue1133 (really more about fixing stuff upstream)
http://bugs.jython.org/issue1460 (isn't this a parser problem?)
http://bugs.jython.org/issue1807 (nothing to do w/ JLine)
http://bugs.jython.org/issue1972 (I just commented on this: I doubt the
*original* issue actually involves JLine AFAICT)

If these issues can't be fixed and disabling is the only option, it should
only be disabled on the problematic platforms, which seems to me to be
Windows/cygwin and certain unixes like AIX.

Seems like the only bug affecting the mainstream POSIX oses (linux/osx etc)
is http://bugs.jython.org/issue1987

Which doesn't justify disabling JLine by default on those platforms in my
opinion. Though we should really fix our getpass to use Java 6's
System.console.readPassword =]

--
Philip Jenvey