And this is not just with Python. Try any other dynamic language (Ruby), send a function in place of a string and see failure msg. And if the question is really about path joins and path manipulations, then I believe PEP 428 ( http://www.python.org/dev/peps/pep-0428/) would be better candidate to address these scenarios.
On Sat, Feb 9, 2013 at 3:45 PM, Eric V. Smith <e...@trueblade.com> wrote: > On 2/9/2013 6:23 PM, Greg Ewing wrote: >> Terry Reedy wrote: >>> I agree. Since the exception type is not documented and since no one >>> should intentionally pass anything but strings, and therefore should >>> not be writing >>> >>> try: >>> os.path.join(a,b) >>> except AttributeError: >>> barf() >>> >>> I think it would be acceptable to make a change in 3.4. >> >> Why should we go out of our way to address this particular >> case, and not any of the infinitely many other situations >> where you could forget to add parens to a function call? >> > > I agree we do not want to go down this slippery slope. The number of > such places in the standard library is huge. The existing error message > is one that a user should be able to understand, since it's so common. > > -- > Eric. > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/senthil%40uthcode.com _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
