This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author xdegaye
Recipients jneb, r.david.murray, xdegaye
Date 2014-03-18.16:40:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1395160804.68.0.938999993762.issue20853@psf.upfronthosting.co.za>
In-reply-to
Content
> There is at least one other place (do_break) where this same problem could crop up.

Also in do_retval. And the exception is silently ignored in do_p and do_pp when repr() fails, which is not correct.

A solution could be to have a message_safe method to be used in such cases. For example, substitute in do_args:

    self.message('%s = %r' % (name, dict[name]))
with:
    self.message_safe('%s = %r', name, dict[name])

def message_safe(self, fmt, *args):
    try:
        print(fmt % args, file=self.stdout)
    except Exception:
        exc_info = sys.exc_info()[:2]
        self.error(traceback.format_exception_only(*exc_info)[-1].strip())
History
Date User Action Args
2014-03-18 16:40:04xdegayesetrecipients: + xdegaye, jneb, r.david.murray
2014-03-18 16:40:04xdegayesetmessageid: <1395160804.68.0.938999993762.issue20853@psf.upfronthosting.co.za>
2014-03-18 16:40:04xdegayelinkissue20853 messages
2014-03-18 16:40:04xdegayecreate