Georg Brandl <ge...@python.org> added the comment: How would you propose to fix this? print() should certainly not catch all TypeErrors and raise a new one...
Maybe exception chaining could be used, so that print raises a TypeError of its own with the cause being the original message? ---------- nosy: +georg.brandl _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6304> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
