[Python-Dev] PEP 435: pickling enums created with the functional API (original) (raw)
Eli Bendersky eliben at gmail.com
Thu May 9 18:47:31 CEST 2013
- Previous message: [Python-Dev] PEP 435: pickling enums created with the functional API
- Next message: [Python-Dev] PEP 435: pickling enums created with the functional API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, May 9, 2013 at 9:31 AM, Barry Warsaw <barry at python.org> wrote:
On May 09, 2013, at 09:24 AM, Guido van Rossum wrote:
>+1. This is a good one. While adding module=name is actually more >typing than passing name + '.Color' as the class name, the current >proposal (parsing for dots) makes it very attractive to do the wrong thing >and hardcode the module name. Then typing the module incorrectly is very >easy, and the mistake is easily overlooked because it won't be noticed >until you actually try to pickle a member. Seems reasonable. The
module
argument should be keyword-only, and obviously namedtuple should support the same API.
Yes, this was already pointed out by Eric in http://bugs.python.org/issue17941 which tracks this feature for namedtuple.
Eli -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20130509/94d5c31c/attachment.html>
- Previous message: [Python-Dev] PEP 435: pickling enums created with the functional API
- Next message: [Python-Dev] PEP 435: pickling enums created with the functional API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]