A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2010-May/100235.html below:

[Python-Dev] Reasons behind misleading TypeError message when passing the wrong number of arguments to a method

[Python-Dev] Reasons behind misleading TypeError message when passing the wrong number of arguments to a method [Python-Dev] Reasons behind misleading TypeError message when passing the wrong number of arguments to a methodCameron Simpson cs at zip.com.au
Fri May 21 03:46:38 CEST 2010
On 20May2010 17:46, Ben Finney <ben+python at benfinney.id.au> wrote:
| Would it help if the traceback showed the ‘repr()’ of each of the
| arguments received? That way it would be much clearer when the instance
| was received as the first argument.

I've occasionally passed large or deep dicts etc to functions and foolishly
printed their repr in debug statements. They can be... wordy.  Maybe a
cropped repr, or the .__class__ attribute?
-- 
Cameron Simpson <cs at zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/

Every technical corrigendum is met by an equally troublesome new defect report.
        - Norman Diamond <diamond at jit.dec.com>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4