Breaking python2.4 compatibility for bzr-2.4

[Alexander Belchenko]

John Arbash Meinel пишет:
> On 04/27/2011 02:07 AM, Martin Pool wrote:
>> OK, so it seems like we can move to at least python2.5 for bzr2.4.
>> The main problem with moving to python2.6 is that is harder to
>> redistribute py2exe binaries on Windows; one main benefit is that it
>> will let us mark b'' byte strings which will help with python3.  A
>> side benefit of sticking with python.5 is that it will keep support
>> for a shipped python interpreter on old linux distributions like
>> Ubuntu Hardy.
> 
> I'm pretty sure that *today* we are already using python2.6 in the
> Windows installer. So while it was indeed harder to get working, we made
> it work.

That's correct. redist stuff behind VS2008 DLLs (used by Python 2.6+) 
makes the *installation* on vanilla machines slightly harder, but it 
does not affect the build process.

>> <https://code.launchpad.net/~jameinel/bzr/test-traceback-767177/+merge/58505>
>> is blocked on deciding about this.  It declares a requirement for
>> python2.5 but it seems like the actual code will work on 2.5.
> 
> I think you meant "John declared a requirement of 2.6, but it would work
> with 2.5" which is true. I can certainly back down. But I figured if I
> was gonna jump, might as well jump high.
> 
>> So I think for now we should go to just 2.5, and then later, perhaps
>> driven by python3, we'll can look at requiring python2.6.  Perhaps
>> even before the bzr2.4 final release (~August).  Perhaps the Windows
>> distribution situation will have improved.
>>
>> Martin
>>
> 
> As mentioned, I'm pretty sure we already bit that bullet for *our*
> packaging. I think that Alexander sometimes recompiles on his own, and
> he hasn't switched yet.

Sometimes I do compile custom bzr.exe to test things, but as "just user" 
I'm using official standalone installer from Launchpad which has Python 
2.6 inside as John said.