increasing the python requirement

[Vincent Ladeuil]

>>>>> Toshio Kuratomi <a.badger at gmail.com> writes:

<snip/>

    > If you do backports of new formats to the version of bzr that supports
    > python-2.4 that strikes a great balance as far as I'm concerned.

Be sure to voice your concern again *if* and *when* we start talking
about a new format.

    > I still have to keep bzr running on RHEL5 for people who use it there until
    > RHEL5 EOLs and the big thing is *not* performance optimizations, new
    > software that targets new APIs, and such... end users understand that those
    > types of things may require a newer version of python/bzr.  It really is just --

    > "I'm running RHEL5 and I need to interoperate with the repository
    > format on launchpad to checkout the latest version of gwibber"

I expect that you'll run into problems from the gwibber side asking for
versions of software components not supported by RHEL5 before you
encounter the same issues with bzr (and again, make sure you make your
issues known as you've done here).

    > or "I'm running bzr smart server on a RHEL5 server and a few of
    > the clients pushing repos get errors because they default to the
    > new format."

This is easier to address as it "only" require that bzr can decide which
format should be the default at a project level (which is not
implemented yet, bialix made a proof-of-concept plugin to ensure this at
a user level so we know it's doable).

But in both cases, while I agree bzr should address both needs, it's
also a project community issue to ensure that all members are aware of
the necessary constraints to interoperate.

  Vincent