[Python-Dev] Split unicodeobject.c into subfiles? (original) (raw)

Chris Jerdonek chris.jerdonek at gmail.com
Fri Oct 5 01:37:10 CEST 2012

On Thu, Oct 4, 2012 at 4:31 PM, Benjamin Peterson <benjamin at python.org> wrote:

2012/10/4 Victor Stinner <victor.stinner at gmail.com>:

I am not siding with either side of the change yet, but an additional argument against is that history may become less convenient to navigate and track (e.g. hg annotate may lose information depending on how the split is done).

If new files are created using "hg cp unicodeobject.c unicode/newfile.c", the historic is kept. Yes, but you can only create one file that way.

You can create multiple files this way. I just verified it. But the problem happens with merging. You will create merge conflicts in the deleted portions of every split file on every merge. There may be a way to avoid this that I don't know about though (i.e. to record that merges into the deleted portions should no longer occur).

--Chris

More information about the Python-Dev mailing list