This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients effbot, gvanrossum, lemburg, loewis
Date 2008-09-10.18:09:23
SpamBayes Score 4.6560453e-06
Marked as misclassified No
Message-id <48C80D51.1090309@v.loewis.de>
In-reply-to <ca471dc20809100911u9c99bbbu4f98e6cd56da33c8@mail.gmail.com>
Content
> That's unfortunate -- perhaps the 2.6 flag and data can be brought in
> line, to make future merges easier?

I thought of that, however, merging the databases themselves would still
not be possible: the 3.0 database has the flags set in many records,
which causes merge conflicts (as the 2.x database has different flag
values). So regenerating the database is necessary, anyway.

In future changes, it might be useful to have new flags with the same
values, so that such patches can be merged without conflicts in the
generator.
History
Date User Action Args
2008-09-10 18:09:24loewissetrecipients: + loewis, lemburg, gvanrossum, effbot
2008-09-10 18:09:23loewislinkissue3811 messages
2008-09-10 18:09:23loewiscreate