Nice - now using a banner doesn't crash bpython-urwid! Thanks!

Next is making possible to use urwid in embed. (locally patched this way to
have flask-script using it since works much better on some terminals.

On Wed, Aug 27, 2014 at 4:22 AM, Thomas Ballinger notifications@github.com
wrote:

Nice - now using a banner doesn't crash bpython-urwid! Thanks!

—
Reply to this email directly or view it on GitHub
#362 (comment).

def embed(locals_=None, args=['-i', '-q'], banner=None, impl='cli'):
    package="bypthon.{0}".format(impl)
    bpython = __import__(package, globals(), locals(), [main], -1)
    return bpython.main(args, locals_, banner)

Something along those lines would be ok for you?

This seems pretty reasonable, although I'm not sure I understand all of what you're proposing - I assume you want a function you can call to run a bpython session with the current scope, and you want to package it with bpython. I'm all for both of those ideas, and the approach above seems good.

You're welcome to continue with this (and I think you should!) but know that soon we're soon going to be changing the way frontends work in bpython and packaging them separately - @ikanobori is undertaking this so knows more about it. I just mean to say that the interface for using a different interpreter is going to change soon and will be different new releases.

Actually the start of the whole deal is wanting flask-script working fine with iterm2 and terminology since they are the terminals I use most, then I found out that the urwid backend seems working well enough and forced embed() to use it directly, discovering that small bug =)

(curtsies support seems requiring an update to support the new version of it)