On Sep 25, 2010, at 01:22 PM, Paul Wise wrote: >On Mon, Aug 23, 2010 at 8:17 PM, Barry Warsaw <barry@python.org> wrote: > >> My guess is that you'd get a lot of push back from folks in >> python-dev. Won't a change like this have the potential to produce >> confusing, wrong, or hard to track down bugs? This kind of implicit >> behavior change seems to run counter to the "explicit is better" >> mantra. >> >> Note too that there's no way this would change before Python 3.2. >> >> I'm not qualified to personally champion this upstream, but I do >> encourage you to submit a bug at bugs.python.org if you feel >> strongly about it. If you can't or don't want to bring it to the >> attention of python-dev, I will do so in a neutral way. > >I missed your mail due to an evil mail provider, but it looks like >doko has filed a bug about this: > >http://bugs.python.org/issue1703592 > >Some particularly insightful comments by cjwatson there. Yep. Unfortunately I don't think upstream can do anything but improve the documentation for Python 2.7. As I followed up in the bug report, I'm +0 for adding a convenience function to Python 3.2 that swallows the exception. -Barry
Attachment:
signature.asc
Description: PGP signature