Atsuo Ishimoto writes: > Okay, we'll keep 'strict' as default error handler for stdout always, > then. I can live with it. > But, my $0.02, I expect this issue will be revisited after people > start to develop real applications with Python 3.x.
I agree, I expect it to be revisited too. But in the meantime - people who need it will have an obvious signal that they need it, - it will be obvious to people who know what's going on how to fix it, - and when the experience needed to decide what use cases matter and which ones are subject to confusion of the kind Guido mentions accumulates, and it gets changed, programs that previously did not throw an error will continue to work as they did. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com