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 madan.ram
Recipients eric.araujo, ezio.melotti, georg.brandl, gpolo, madan.ram
Date 2013-11-27.10:10:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385547045.38.0.843948844606.issue19810@psf.upfronthosting.co.za>
In-reply-to
Content
I found that it will be useful to show the list of function arguments using inspect module. When the function executed by the user in interpreter as "TypeError". 

ex: - 

>>def foo(a,b=4,c="hello"):
...     print a,b,c

>>foo()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: foo() takes at least 2 arguments (0 given)

Rather the displaying like above it is will be much more readable to show as below.

>>foo()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: foo() takes at least 1 arguments args=['a', 'b', 'c'], varargs=None, keywords=None, defaults=(4, 'hello') (0 given)

This will be advantageous when the user has forgotten what parameter to use for builtin function when working offline.
History
Date User Action Args
2013-11-27 10:10:45madan.ramsetrecipients: + madan.ram, georg.brandl, gpolo, ezio.melotti, eric.araujo
2013-11-27 10:10:45madan.ramsetmessageid: <1385547045.38.0.843948844606.issue19810@psf.upfronthosting.co.za>
2013-11-27 10:10:45madan.ramlinkissue19810 messages
2013-11-27 10:10:44madan.ramcreate