Hi Terje (and the mailinglist),
I have fixed your issue in my latest commit in tip. I can now run
bpython when I create a panel entry for bpython-gtk. Maybe you can
confirm?
You can see the commit here if you are interested, but it's just some
added abstraction so that bpython.gtk_ can override what it does when
stdin is not a tty. http://bitbucket.org/bobf/bpython/changeset/7cf1adb41438/
Thanks for reporting the bug and going to such lengths to determine
the cause!
Regards,
Simon de Vlieger
On 7 apr 2010, at 10:16, Bob Farrell wrote:
This guy was kind enough to do some debugging and found the problem
- should be
nice and simple but we could have easily missed tihs in a release.
Hooray ! \o/
-------------------------------------------------------------------------------
Hi Bob,
I have a strange problem with bpython-gtk in 0.9.6.2 and (latest git
(0.9,7)).
I can launch it from a terminal and it works just fine.
However, when I add a button to my GNOME or KDE panel to easy start
bpython-gtk
by clicking I just get ... nothing. No window. From .xsession-errors
I see:
plasma-desktop(1584)/plasma
Kickoff::RecentApplications::Private::addEntry: Duplicate entry added.
Removing existing entry from queue.
plasma-desktop(1584)/plasma Kickoff::RecentApplications::add: Recent
app
added "bpython-gtk.desktop" 3
plasma-desktop(1584)/plasma
Kickoff::RecentlyUsedModel::Private::removeExistingItem: Removing
existing item 0x17abe10
klauncher(1547)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying
to open ksycoca from "/var/tmp/kdecache-terjeros/ksycoca4"
kdeinit4: preparing to launch /usr/bin/bpython-gtk
klauncher(1547)/kio (KLauncher) KLauncher::processRequestReturn:
"/usr/bin/bpython-gtk" (pid 13281) up and running.
kwin(1580) KWin::Workspace::updateClientArea: screens: 1 desktops: 4
kwin(1580) KWin::Workspace::updateClientArea: Done.
Let's see....
Okay, I found it with some old fashion print debugging.
It's here in bpython/args.py:85
if not (sys.stdin.isatty() and sys.stdout.isatty()):
interpreter = code.InteractiveInterpreter()
interpreter.runsource(sys.stdin.read())
raise SystemExit
which is called from bpython/gtk_.py:635
config, options, exec_args = bpython.args.parse(args, gtk_options)
When running from the GNOME/KDE panel sys.stdin.isatty() and
sys.stdout.isatty() is both False.
And bpython stops without a trace. When using gtk these returning True
is not needed?
Should not be hard to fix this issue?
- Terje
--
Bob Farrell
--
You received this message because you are subscribed to the Google
Groups "bpython" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/bpython?hl=en
.
--
You received this message because you are subscribed to the Google Groups
"bpython" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/bpython?hl=en.
