christian heimes wluhecheimesde guido van rossum wrote doesnt address merges suppose c code thats shared 26 30 manipulates binary data eg gzip codec currently uses pystring branches changes trunk merge smoothly py3k branch change pystring pybytes py3k branch every change make 26 code cause merge conflict really want worry effectively separate trunk py3k branch losing advantage development effects im fully aware extra burden removal pyint_ functions already causing merge conflicts compile errors nearly every c code merge contains least one place requires manual intervention pyint merge conflicts trivial fix would errors caused pystring pybytes rename im worried extra work since usually trivial fast fix im worried api names really want drag dead bodies along road next ten years dead bodies going rot stink sooner later python 32 everybody surely regrets confusing names christian _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom wed 06 aug 2008 114613 0100 python3000 26 30 tasks