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

Showing content from https://mail.python.org/pipermail/python-dev/2013-December/130756.html below:

[Python-Dev] How long the wrong type of argument should we limit (or not) in the error message (C-api)?

• Previous message: [Python-Dev] How long the wrong type of argument should we limit (or not) in the error message (C-api)?
• Next message: [Python-Dev] How long the wrong type of argument should we limit (or not) in the error message (C-api)?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Sun, 15 Dec 2013 09:10:08 +1000
Nick Coghlan <ncoghlan at gmail.com> wrote:
> 
> The question should probably be addressed directly in PEP 7, and I'd
> be inclined to just bless the "%.400s" variant for future code.

Shouldn't we have a special "%T" shortcut instead of trying to
harmonize all the occurrences of `"%.400s", Py_TYPE(self)->tp_name` ?

Sprinkling the same magic number / convention everywhere doesn't sound
very future-proof, nor convenient.

Regards

Antoine.

• Previous message: [Python-Dev] How long the wrong type of argument should we limit (or not) in the error message (C-api)?
• Next message: [Python-Dev] How long the wrong type of argument should we limit (or not) in the error message (C-api)?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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