[Python-Dev] [Python-checkins] r86355 - python/branches/py3k/Modules/_pickle.c (original) (raw)
Alexander Belopolsky alexander.belopolsky at gmail.com
Wed Nov 10 21:48:38 CET 2010
- Previous message: [Python-Dev] [Python-checkins] r86355 - python/branches/py3k/Modules/_pickle.c
- Next message: [Python-Dev] [Python-checkins] r86355 - python/branches/py3k/Modules/_pickle.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Nov 10, 2010 at 7:28 AM, Victor Stinner <victor.stinner at haypocalc.com> wrote: ..
I don't know, but the commit is trivial and cheap. If it improves the support on uncommon compiler, I agree to commit such change.
But it does it at the cost of invalidating the "svn blame" for the last enum entry now and for future additions. The problem is that when you change from
enum { .. X }
to
enum { .. X, Y }
you modify the X line while you are not responsible for adding the X entry. Someone who will then add Z, will be blamed for Y as well.
- Previous message: [Python-Dev] [Python-checkins] r86355 - python/branches/py3k/Modules/_pickle.c
- Next message: [Python-Dev] [Python-checkins] r86355 - python/branches/py3k/Modules/_pickle.c
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]