On Sat, May 15, 2010 at 14:30, Sugar Labs Bugs <bugtracker-nore...@sugarlabs.org> wrote: > #1755: sugar-emulator: better error message if X server is unreachable > ------------------------------------------+--------------------------------- > Reporter: sascha_silbe | Owner: sascha_silbe > Type: defect | Status: accepted > Priority: Unspecified by Maintainer | Milestone: 0.88.x > Component: sugar | Version: Git as of bugdate > Severity: Trivial | Keywords: r? > Distribution: Unspecified | Status_field: Assigned > ------------------------------------------+--------------------------------- > Changes (by sascha_silbe): > > * cc: tomeu (added) > * keywords: r! => r? > > > Comment: > > Replying to [comment:3 tomeu]: > > + sys.stderr.write('Error executing server: %s\n' % (exc, )) > > Better print the full exception including the traceback? > That will add no useful information and instead confuse the user.
This surprises me, am I the only one that hates having to grep the source for an error message because someone ate the traceback? Regards, Tomeu > > + if not pipe: > > + if not server: > > Always use "is None", classes implementing a collection protocol > evaluate to False when empty. > Changed. > > -- > Ticket URL: <http://bugs.sugarlabs.org/ticket/1755#comment:4> > Sugar Labs <http://sugarlabs.org/> > Sugar Labs bug tracking system > _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel