guido van rossum hoaufpythonorg sun mar 16 2008 104 pm christian heimes wrote 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 even though popular pyint_ apis still available even macros nearly every c code merge contains least one place requires manual intervention pyint merge conflicts trivial fix would errors caused pystring pybytes rename disagree bad merges already frequent cause instability 30 could easily double problems want reduce instability really wish would commit unittests pass also dont want merges cost time 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 doesnt black white using macro approach propose fix situation time later could also make changes 26 26 code looks 30 however binary compatibility think would better 26 linker sees pystring 30 sees pybytes guido van rossum home page httpwwwpythonorgguido _______________________________________________ python3000 mailing list smsbmo9552pythonorg httpmailpythonorgmailmanlistinfopython3000 unsubscribe httpmailpythonorgmailmanoptionspython3000python300040tangomucom wed 06 aug 2008 055142 0500 python3000 26 30 tasks