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/2018-October/155622.html below:

[Python-Dev] Standardize error message for non-pickleable types

[Python-Dev] Standardize error message for non-pickleable types [Python-Dev] Standardize error message for non-pickleable typesSerhiy Storchaka storchaka at gmail.com
Tue Oct 30 04:12:45 EDT 2018
29.10.18 23:17, MRAB пише:
> 1. If you're pickling, then saying "pickle" is more helpful.
> 
> 2. In English the usual long form is "cannot". Error messages tend to 
> avoid abbreviations, and also tend to have lowercase after the colon, e.g.:
> 
>      "ZeroDivisionError: division by zero"
> 
>      "ValueError: invalid literal for int() with base 10: 'foo'"
> 
> 3. If it's failing on an object (singular), then it's clearer to say 
> "object".
> 
> 4. Articles tend to be omitted.
> 
> 5. Error messages tend to have quotes around the type name.
> 
> Therefore, my preference is for:
> 
>      "cannot pickle 'XXX' object"

Thank you Matthew, I'll use your variant.

Will something change the fact that in all these cases the pickling will 
be failed not just for specific object, but for all instances of the 
specified type?

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